User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b4) Gecko/2008030318 Firefox/3.0b4 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b4) Gecko/2008030318 Firefox/3.0b4 The border-width of a treecol element is not computed correctly. DOM Inspector shows a rule from chrome://global/skin/tree.css setting ie. border-top-width to 2px while the computed style shows border-top-width of 5px (all the border widths are 5px and should be 2px). This can be easily seen by inspecting the about:config page with DOM inspector. This is a regression - border width of treecol can be styled in Firefox2. Happens with linux build 3.0b4 and 3.0b5 (possibly others but not tested). Probably works ok on windows (did just a quick check and will try to recheck tomorrow when I have access). Reproducible: Always
Are you sure its not the border provided by the native theme?
What exactly is "the native theme"? I was under the impression that all xul interface can be styled by CSS. Is that no longer true for Firefox3 on Linux? I checked that in Firefox2 the layout of treecol element follows the rules set in tree.css. If there is anything I can do, let me know. It sure looks very ugly and takes a lot of screenspace (ie. the treecol row is actually higher than the menu row, it is even 1px higher than the url textbox and I've found no way so far to change it).
Reporter, are you still seeing this issue with Firefox 3.6.x or later in safe mode? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
I have checked 3.6.8 in safe mode and in regular mode and the appearance is the same. Also the only difference from 2 years ago is that the computed style shows 4px instead of 5px while the tree.css still requests 2px (tested on ubuntu). If this is a feature I was not able to find any documentation for it.
No reply, INCOMPLETE. Please retest with Firefox 3.6.10 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.