Closed (fixed)
Project:
FCKeditor - WYSIWYG HTML editor
Version:
6.x-1.4-rc1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Sep 2008 at 22:51 UTC
Updated:
6 Oct 2009 at 12:13 UTC
No mater what I do I still get top border for my table in D6.4 using latest FCKeditor. I made the border attribute zero and even created style for my table with ; border-top:none, zero but still have a top border in FireFox and Chrome
This is an example
http://kirmashan.com/drupal/?q=node/13
Ten I realized also that FCK change my style border:none to border: medium none. This happen every time I save the file.
Comments
Comment #1
amir simantov commentedI have the same problem with several sites. However, border code is shown correctly in the source code, that means:
border="0"
Comment #2
Jorrit commentedIt's actually a border-top on the tbody element, which is drupal default. You can try to override it for tables in div.content by using:
This code is untested, check if it works for you.
Comment #3
Jorrit commentedClosed because of inactivity.
Comment #4
amir simantov commentedThanks Jorrit - that helped :-)
Amir
Comment #5
amir simantov commentedI open it again. For some reason, this fix in the CSS does not solve the problem any more.
Comment #6
tolaemon commentedI had the same problem with the top of the tables: every time I added a table into a content with FCK, a grey line apeared in the top of the table. I used Mozilla's Web Developer plugin to locate the cause of the problem and found that one of the .css was overidin my table configuration. This css was the system.css located into the modules/system/ folder:
tbody {
/* border-top: 1px solid #ccc; */
}
I comented the "border-top: 1px solid #ccc;" line and the problem disapeared. Anyway I'm not sure if doing that is a good Drupal practise because Drupal's default files shoud stay unmodified, but the fact is that is the only way I've been able to solve this issue.
Hope it helps to you too.
Comment #7
Jorrit commentedI am closing this issue as it is not really an FCKeditor problem.
Comment #8
amir simantov commentedThanks tolaemon!