The Gecko HTML layout engine used in Firefox has excellent CSS support. Not perfect of course, but excellent at least. This post started its life as an announcement of what I thought (at the time) might be a bug in Firefox’s CSS handling. The ‘bug’ turned out to be an oversight on my part and it’s accompanying blog entry an embarrassment. I have since transformed my mistake into something hopefully useful to you dear Googler.
Your problem with CSS in Firefox is probably a problem with CSS. The Gecko compatibility handbook on the Mozilla developer centre site outlines some differences with other browsers that commonly cause problems for web developers.
If you are still convinced there is something buggy happening first try validating your HTML then validate your CSS. Install the very useful Web Developer extension for Firefox. It allows you to validate HTML pages which are not yet to accessible on the web with the W3C Markup Validation Service. This will ensure you don’t make my mistake.
Finally, if your valid code is still causing you grief, the best listing of Bug Reports for Mozilla I could find. Personally I’m yet to encounter any of the issues listed here, it’s Internet Explorer that generally causes my headaches.
Update 22 February 2006
I have completely rewritten this post. There was no bug. That will teach me for not checking for odd invisible characters. I guess I could have hesitated a little longer.
Some further investigation has bought me a step closer to the source of these little gremlins. Every abbreviation that I recently imported from TypeIt4Me into my new installation of Textpander has one hiding at the end of the resulting inserted string. Retyping the content in Textpander preferences fixes the problem.
Version of 1.1 of Textpander addresses this.