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."
Right. So none of the browsers tested can display the test page correctly? And they're the best, most compliant browsers available?
And they've had how long to get it right?
In that case, it would seem to me that it is the standard that is broken, if it's really that difficult to render a page with a cascading style sheet.
(Spudley Strikes Again!)
like
safari on tiger anyone ?
please post a screenshot of that I would really be intrested
stats on web browsers market share
w3 numbers
At the end of the day, no it's not. Broken is broken.
So when Firefox applies the display: table-cell rule correctly, that's utterly meaningless and should be filed as a bug because Firefox applies other rules on the same page wrongly? You aren't making sense.
There are many, many CSS rules in the test. The test is designed to exercise lots of different areas of CSS.
If you think that there's no useful information beyond "no browser applies all of the rules correctly", well then you've wasted your time reading this story, because I could have told you that before this test was even published.
Let's all pat the OSS Community on the back!
What does open-source have to do with this? Opera, a tiny company with nowhere near the resources of Microsoft, who haven't released their browser as open-source, have done miles better than Microsoft.
I think you're just trolling, especially when you try and turn this into some kind of open-source vs proprietary flamewar.
Just out of curiosity...what browser did they use to get the successful reference rendering? I'm presuming there's one that successfully renders, otherwise, how do they know their test code is valid? I've clicked around but don't know what they used to generate that png.
"Hardly used" will not fetch you a better price for your brain.
I'm confused, is this supposed to be valid CSS2? The W3C CSS validator finds 8 errors in the page.
.parser-container div .parser .parser .parser .parser .parser
-molo
CSS validator results
* Line: 46
Parse Error - second two]
* Line: 91 Context :
Invalid number : color orange is not a color value : orange
* Line: 97 Context :
Property error doesn't exist : }
* Line: 100 Context :
Property m rgin doesn't exist : 2em
* Line: 100
Parse error - Unrecognized : };
* Line: 102 Context :
Invalid number : width only 0 can be a length. You must put an unit after your number : 200
* Line: 103 Context :
Parse Error - ! error;
* Line: 103 Context :
Parse error - Unrecognized : }
Using your sig line to advertise for friends is lame.
At the end of the day, I'd like to drive home in the car that's timing is a little off causing a loss of 2 mpg and 3 hp, as opposed to the car that is in such a state of disrepair that the axle falls off after 2 miles and the fuel tank spontaneously combusts.
There's also the idea that, assuming all parties are working to make their browser compliant, then it may also be assumed that one party may be closer to reaching full complaice than the other.
Or, to further mutilate an abused analogy, which of the above cars would be easier to repair?
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
What publicly availbe browser can, if any? Because I would love to try it.
Fair and balanced as always!