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."
What is the page supposed to look like when rendered???
"Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
yep I think its wrong in a couple of places for sure
Line: 91 Context : Invalid number : color orange is not a color value : orange
as any good web dev should know the list of keyword color names is: aqua, black, blue, fuchsia, gray, green, lime, maroon, navy, olive, purple, red, silver, teal, white, and yellow.
if you want a rgb colour (I use english from england ) then color: rgb(255,0,0)
also the error
Line: 102 Context : Invalid number : width only 0 can be a length. You must put an unit after your number
length : Specifies a fixed width.
percentage : Specifies a percentage width. The percentage is calculated with respect to the width of the generated box's containing block.
auto : The width depends on the values of other properties.
Negative values for 'width' are illegal.
For example width: 200px
regards
John Jones
please correct me if I am wrong
Webstandards.org may have good intentions, but I'm not sure I trust their test or their organization. For one thing, someone has pointed out that the W3C's CSS validator rejects it. (This link currently slashdotted.)
Gecko renders part of the second row of the face at the right edge of the viewport. I believe that that is actually the correct behavior according to the specifications. Row 2 is generated by
The blockquote is a block-level element with unspecified width, so except for the 60px left margin, it should occupy the entire width of the containing block (CSS 2.1, Sec 10.3.3). Therefore, the address element, which is floated to the right within the blockquote, is correctly placed at the right edge of the viewport. I don't see why the "shrink-to-fit" rule for computing the width of the blockquote should apply as they claim it does. There may be other errors, but I haven't investigated further.
When the W3C publishes a test, one can be pretty sure that it's authoritative. But who is behind webstandards.org? They claim to be a grassroots coalition, yet I don't see where on their website they invite site visitors to join or contribute to their cause.
Their explanation of the test lacks a contact address at the end to report errors. It seems rather careless of them to publish the test in that state, and it doesn't inspire confidence in the rest of the test.
It's good to see someone making an effort. I do hope that this test will help browsers improve, but I wouldn't trust that the test itself is 100% accurate, either. I would love to see the W3C devise more compliance tests of this sort.
Don't know if I'm just missing something, admitedly I've only skimmed over the tour, but how did they actually render it?
If firefox (and thus I'd assume mozilla), ie, opera, and konqy (as tested by me in kde-3.4) all fail, what browser is so great it does it properly?
Is it open-source? Can it's code be used as a reference for the other open-source browser?
Where did they get the reference image?