What CSS bugs exist with mozilla?

[imaginecss]

I was doing some IE 7 / mozilla site testing the other day and my site looks fine in IE 7 with STRICT XHTML mode on. However when I view it Mozilla, I'm seeing some visual displacement that should not be there because the code is CSS correct.

So I'm not sure which to trust, since the mozilla rendering engine is a bit out date compared to IE 7.0 now.

[icantthinkofone]

IE7 is eight years behind web standards and does a poor implementation of CSS code. Firefox does a very good job of the CSS2.1 implementation. You should NOT trust IE6 or IE7 due to its bugs and quirks. ALWAYS design using Firefox or Opera. Then adjust for IEs bugs.

Post your complete code so we can help you.

[doodlebee]

I'd like to also put in there that Mozilla Firefox doesn't always pass the acid2 test - but Opera does. So if you aren't sure, check it in Opera 9 and see if Firefox is closer to the "good site" - I'll betcha it is.

And by the way, IE7 is *still* in Beta. It's not yet been officially released.

[icantthinkofone]

IE7 is 'code complete' meaning there will be no further improvements to its rendering engine. Also, it has reached RC1 status and no longer in beta.

[amznVibe]

Actually doodlebee, there is a branch of Firefox that does pass Acid 2, called the "reflow" branch but it's not in use yet.

[flickr.com...]
Slightly OT sorry, but it's very interesting, no?

[SuzyUK]

since the mozilla rendering engine is a bit out date compared to IE 7.0 now

No sorry, I do think you do have that a bit back to front.
With IE7, MS have just tweaked their outdated engine in order to attempt to bring its rendering more inline with what we expect (thanks to the better rendering engines out there). They are still nowhere close to FF/Opera/Safaris Engines yet IMHO. Plugging holes with a filler will not give the same strength as building anew? case in point is "hasLayout", a Microsoft proprietary property, it still exists they just did something to make the more obvious side effects go away, but it is still there!

Therefore if it where me I would still be trusting what I'm seeing in Mozilla. Haven't yet found a specific Mozilla CSS "Bug", it used to have with overflow, but that has been fixed

I'm seeing some visual displacement that should not be there because the code is CSS correct.

It doesn't matter how correct the code is, it's whether the browser rendering the code understands how it supposed to render it. e.g. I think default margins, collapsing incorrectly with floated elements is still an IE/Moz difference in interpretation of the recommendations.

Suzy

[encyclo]

For a good list of Gecko CSS bugs (Gecko is the rendering engine used by Mozilla products such as Firefox, SeaMonkey, Mozilla Suite...) you can consult this CSS support chart:

[developer.mozilla.org...]

Mozilla claims 100% CSS1 compliance. In reality they don't support some of the more obscure parts of CSS, for example

@font-face

.

[icantthinkofone]

So, then, mozilla is NOT claiming 100% compliance.

[encyclo]

mozilla is NOT claiming 100% compliance

No, they are claiming 100% compliance, just that they are not 100% compliant. ;)

Most browsers claim 100% CSS1 compliance, and most bugs you will encounter is not wih CSS1 but with CSS2 implementations. You can get rendering differences between two browsers even when both handle the CSS specification in exactly the same (compliant) way, because there are no defined guidelines for browser defaults. One browser can set a default bottom margin on a

h1

element as 1.5em and another at 1.2em, and both would be correct.

[icantthinkofone]

What I'm saying is you said mozilla claimed 100% compliance yet you point to a mozilla site that says, no, they don't support that, and at least one other, css attribute so how are they claiming 100% compliance?

(I don't want to come across as starting to nit-pick this and escalating into some big stupid argument ;) )