Recommended Posts

The Web Standards Project (WaSP) today announced the release of Acid3, the latest in a line of tests designed to expose flaws in the implementation of mature Web standards in Web browsers. By making sure their software adheres to the test, the creators of these products can be more confident that their software will display and function with Web pages correctly both now and with Web pages of the future.The Acid3 Test is designed to test specifications for Web 2.0, and exposes potential flaws in implementations of the public ECMAScript 262 and W3C Document Object Model 2 standards. Collectively known as DOM Scripting, it is these technologies that enable advanced page interactivity and power many advanced web applications such as web-based email and online office applications.

As a series of 100 mini-tests, Acid3 has already been found to expose flaws in all tested browsers, including Internet Explorer, Firefox, Opera, and Safari. WaSP hopes that Acid3 will prove useful to browser makers during the development of future versions of their products.

WaSP has a history of such initiatives. In 1997, emeritus member Todd Fahrner, together with a group of crack Web developers dubbed the ?CSS Samurai,? created an ?Acid Test? that highlighted shortcomings in browser support for CSS. The Acid Test was instrumental in moving the industry much closer to the goal of consistent rendering of Web pages in different browsers. This was followed by Acid2 in 2005, designed to expose flaws in the implementation of mature Web standards such as HTML, CSS, and PNG. Acid3 builds on and extends this legacy to web applications in 2008.

The Test: http://acid3.acidtests.org/

Source: http://www.webstandards.org/press/releases/20080303/

Will we see a '100' scIE9>I:)? :)

Link to comment
https://www.neowin.net/forum/topic/623574-acid-3-the-web-browsers-test/
Share on other sites

Webkit so far:

Picture%202.png

Yeah, WebKit caused a few problems :laugh:

...

Also, I have to say, it was quite difficult to find standards compliance bugs in WebKit to use in the test. I had to go the extra mile to get WebKit to score low! This was not the case with most of the other browsers.

...

http://ln.hixie.ch/?start=1204593554&count=1

Does this test actually really even matter? Really? All my website load nicely in Firefox 2. Anyway, the IE Epic Fail's are funny. :laugh:

Yeah, it is important (it tests to see if the app works correctly, failing a test means you're doing something wrong, or don't support it at all)

Goes to show one thing. Acid 3 means nothing towards joe user. Standards are great and a "goal" but design to users!

I agree, 60 to 70% of the users of ie have internet explorer 6, so everytime I designed a website I need to make sure that looks good first in version 6.

I agree, 60 to 70% of the users of ie have internet explorer 6, so everytime I designed a website I need to make sure that looks good first in version 6.

lol, I just add a bit of Javascript that tells them to get Firefox or Safari to display the webpage properly, obviously it wont display if the browser is Firefox, Safari, Opera etc

Here are some of mine,

WebKit, Safari 3, and Crappy Internet Explorer <-- who actually still uses that?

haha "porn". nice. i got it hidden in my bookmarks menu. ;)

however, with safari i get the common 39, with webkit 87 or something.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.