Linked by Thom Holwerda on Fri 10th Mar 2006 19:59 UTC, submitted by HankPowers
Permalink for comment 103405
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2005-12-30
QUOTE *Correct me if I'm wrong, but I've heard that Acid2 Test isn't all about 100% pure standards, but instead includes some non-standard codes to see whether the web browser ignores non-standard codes or not.* /QUOTE
You are correct about that. Reading the info at http://www.webstandards.org/act/acid2/guide.html confirms just that. This is what they say:
QUOTE *Acid2 tests features that web designers have been requesting. Everything that Acid2 tests is specified in a Web standard, but not all Web standards are tested. Acid2 does not guarantee conformance with any specification. After careful consideration, we have selected and are testing the features we consider most important for the future of the web. Although Acid2 was inspired by Microsoft's announcement of IE7, it is not targeted at a specific browser. We believe Acid2 will highlight problems in all current browsers./QUOTE
In essence, it tests a browsers support for the features that web designers have been requesting in hopes that those requests will soon become a reality.
It's like "I double-dog dare you, no, I triple-dog dare you" in hopes that they can trick the browser developers to take on the challenge, so the coders get what they want, hehe
sneaky, sneaky :-)