Slashdot Mirror
Firefox and Opera Fail the Acid2 Test
naylor83 writes "Four weeks ago, Opera's CTO Håkan Lie put forward the Acid2 challenge to the IE developers at Microsoft. The Web Standards Project has now silently published the promised browser test. Somewhat surprisingly, both Opera and Firefox fail to correctly render the test page. Obviously though, they're no where near as lousy as Internet Explorer. More screenshots are available at my blog, as well as at other people's."
It's not fud...
did you look at the FF rendering and the IE rendering? Neither is perfect, but the IE rendering is absolutely horrid.
Jay | http://oldos.org
http://webstandards.org/act/acid2/reference.html == proper rendering
http://webstandards.org/act/acid2/test.html#top == test page
Jay | http://oldos.org
Not even Firefox supports all of CSS2.
Google found an article that describes this in more detail
Which part of "obviously" is Fear, Uncertainity or Doubt? It's common knowledge that IE6 is far behind in implementing the W3C web standards.
None, they used something like Gimp or Photoshop. I asked them.
I think he was probably looking for something more like https://bugzilla.mozilla.org/show_bug.cgi?id=28948 0 for Firefox. Check the bugs that that one depends on.
It's supposed to be invalid. The CSS specification defines error handling, and Internet Explorer gets it wrong. A conforming user-agent would never apply those rules.
In fact it is necessary for this stylesheet to be invalid - otherwise it wouldn't test the error handling parts of the CSS specifications.
They deliberately made errors which the browsers should cope with according to the specs.
Firstly, the errors are there on purpose, to check the error handling conformance.
As for whether the <textarea> is shrink-to-fit or not, the CSS 2.1 specification has this to say.
The "rule number three" says that it is shrink-to-fit.
Your mistake is in referring to 10.3.3, which explains what to do for non-replaced block-level elements in normal flow. You should be referring to 10.3.7, which explains what to do for non-replaced block-level elements that are absolutely positioned.
Also, don't get me started on performance. 3 machines in the lab range between 300Mhz celerons with 96MB ram and an IBM Personal Computer 300 (600Mhz celeron with 96M ram). Firefox on those is a no-no. Not only b/c painfully slow startup times, but also, painfully slow rendering of pages. Opera renders pages faster while running a kernel compile in the background than Firefox does on an idle computer. What's there in gecko that makes it so much slower than Opera or khtml? (Yes, you heard it right, starting Konqi from a foreign - Blackbox - wm is actually much faster both in startup and rendering of pages than firefox).
These slow machines function as simple 'terminals' btw - they have opera, gaim, xmms, rox - that can be choosen from a simplified menu.
This must be said at the risk of loosing karma (I have plenty, so go ahead) - there is something wrong with Firefox and its rendering engine, not only in compatibility or correct rendering of pages, but in performance as well. And this is not a minor issue, the performance difference b/w say opera or khtml and gecko is significant. So I have only one demand: inform the potential users correctly, don't give them the false impression that Firefox is better in every way than IE. It is not, and such misinformation will only create a backlash. 2 of those users are now actively looking for more and more justfications to have IE back as the standard browser. They are not interested in philosophy or open source ideals. They are interested in accessing the sites they want.