The Web Standards Project » Acid2 Working together for standards Fri, 01 Mar 2013 18:30:30 +0000 en hourly 1 Acid 2 Test Back to Normal Fri, 25 Jul 2008 02:11:37 +0000 feather For a while now we’ve had a problem with the Acid 2 Test on the WaSP site. If you’re unfamiliar with the Acid 2 Test, it is essentially a test for browser vendors to use as a means to gauge their standards compliance. If your browser renders the Acid 2 Test page the same as the Acid 2 reference rendering, then you know you’re hitting the mark.

I’ll be honest: over the last 10 days, I’ve learned more about the Acid 2 Test than I ever wanted to know. If you want to do the same, you might start with Acid 2: The Guided Tour.

The short version is that part of Acid 2 is a test for the way a browser handles an <object> element when the data attribute references a URL that returns an HTTP status code of 404. A number of caching rules, mod_rewrite rules and redirects all collided to create a problem with our 404. The cached version of our 404 page was returning an HTTP status of 200. As you might expect, this basically makes the test useless.

Acid 2 was broken. Now it is not. Carry on.

]]> 1
What’s the best test for Acid3? Wed, 16 Jan 2008 08:17:07 +0000 Kimberly Blessing Perhaps you expected this announcement, given the news that IE8 passes Acid2. Or maybe it already seems like old news, if you caught the recent Slashdot post. In either case, the news is true — Acid3 will be coming soon!

Whereas Acid2 tested static HTML and CSS, Acid3 will focus on ECMAScript and DOM — the dynamic side of the Web. While it will include a few rendering tests to make things look interesting, the core of the test will be 100 scripting subtests.

And that is where you can contribute! Ian has compiled 84 of the 100 scripts but is seeking 16 additional tests. If you’re up to the challenge, read the criteria, create your test, and submit it — within the next five days!

As with Acid2, the Web Standards Project will play host to Acid3… so stay tuned for the final test, and the play-by-play on the browsers’ progress!

]]> 42
IE8 passes Acid2 test Wed, 19 Dec 2007 20:53:43 +0000 blawson Blimey. Cor luvvaduck and no mistake. Just after the announcement that Opera are complaining to the European Union about Internet Explorer’s dodgy standards support, Chris Wilson reports that an internal build of Internet Explorer 8 passes the Acid2 test.

This doesn’t necessarily mean that IE8 has fixed all its float oddities, or its hasLayout hilarities. But what it does mean is that there is another browser war, and Microsoft did decide to come.

Added 20 December 2007: Markus Mielke of the Internet Explorer team confirms “HasLayout will be history with IE8“. Exciting times…

(This post translated into Polish.)

]]> 50
Safari 3 Public Beta for Mac and Windows Tue, 12 Jun 2007 06:07:10 +0000 Kimberly Blessing As the Apple Worldwide Developers Conference kicked off today, Steve Jobs announced the availability of the Safari 3 Public Beta — for both Mac and Windows. Download it here.

I’ve only just installed it on Windows XP, but it has frozen once and crashed once already. There are complaints of blurry fonts and security bugs. It’s not rendering the Acid2 test correctly. (In fact, it’s not rendering the WaSP site correctly either. I assume the same is true on the Mac, but can someone verify?)

Don’t forget to send in your bug reports via the WebKit bug reporting form or the browser itself (Help > Report Bugs to Apple).

]]> 85
Acid2 and Opera 9 Clarifications: Yes, Opera 9 Passes the Test Fri, 21 Jul 2006 01:01:12 +0000 mollyeh From Ian:

  1. The image changes when you scroll: Not a bug. This is part of the
    test’s checking of fixed positioning.
  2. The image changes when you resize the window such that the text in the becomes jagged when you zoom in. It should not; just like the text, it should remain smooth.
  3. The image breaks dramatically if you enable “Fit to Width” mode: This is a standards compliance bug, but it is by design. Fit to Width works by ignoring the specs. In this case, however, it shouldn’t need to change anything, and is therefore IMHO a bug; but it is not something that affects whether the browser complies to the test or not since anything that happens in “Fit to Width” mode is done with the understanding that it will probably violate the specs.
  4. The image breaks dramatically if you enable “Small Screen” mode: Same as “Fit to Width” mode, but more so.
  5. The image breaks if you change any of the user rendering preferences (e.g. colours, fonts): Not a bug. If you change the preferences, then you are changing how you want the test to look. Tests should only be tested with all the preferences set to their initial values.
  6. The eyes go orange if you view the test zoomed in or zoomed out: This is a bug. The image should get bigger as you zoom in, but it should not change colour. Another bug is that the nose becomes jagged when you zoom in. It should not; just like the text, it should remain smooth.
  7. The nose goes blue if you hover it: Not a bug. This is part of the test.
  8. The eyes disappear and show red if you disable images then reenable them: This is a bug. The eyes should disappear (and say “ERROR”, if I’m not mistaken) when you disable images, but when you reenable them, they should return to the normal rendering.

So in conclusion: There are some standards compliance bugs (6 and 8 above), they are both exposed by the more advanced features that Opera has compared to other browsers. There are also a couple of minor UI bugs (2, 3, 4), but they don’t affect the WaSP’s mission.

An additional note from Håkon Lie points out that “When taking the test, you should use the default settings of the browser you are testing. Changing the zoom level, minimum font
size, applying a fit-to-width algorithm, or making other changes may alter the rendition of the Acid2 page without this constituting a failure in compliance.”

]]> 26
Acid2 and Opera 9 Problems? Thu, 13 Jul 2006 15:59:06 +0000 mollyeh Acid2 under certain unique scenarios. We'd like to hear from you in comments if this is the case.]]> If you’re running across any problems with the rendering of Acid2 in Opera 9, please comment below and let us know the following:

  • OS and version
  • Screen resolution settings
  • Does the test resolve on refresh?

If you can do a screen grab of your results as well, and pop ‘em up on a server somewhere and provide the URL, that’d be great too.

]]> 61
Acid2 Supported in Opera One Year Later Tue, 28 Mar 2006 21:44:47 +0000 mollyeh Acid2 is a year old now, and recent beta builds of Opera 9 now support the test. Håkon Wium Lie, CTO of Opera Software and one of the contributing authors to the Acid2 test, says:

“Some people thought Acid2 would be easy for Opera since we were involved in shaping the test. Not so. Acid2 rightfully exposed many bugs in Opera and we have squashed them, one by one.”

The next challenge for Opera? “Getting that smiley face on phones” Lie says.

There’s also mumblings regarding an Acid3 test or suite, this would be authored by a collaborative group including representatives from major browser and software developers.

]]> 35
Prince 5.1 Passes Acid2 Sat, 10 Dec 2005 13:26:40 +0000 chrisk Prince, a program that converts XML documents styled with CSS into PDF files for printing, has passed the Acid2 test. While Prince isn’t a browser per se — it’s a file converter — it does join Konqueror and Apple’s Safari as the first CSS & HTML implementations to pass the WaSP’s Acid2 Test (disclosure: Håkon Wium Lie, one of the authors of the Acid2 Test, is on the board of YesLogic Pty Ltd).

Congratulations, guys! Nice work.

]]> 0
We love to see you smile Tue, 01 Nov 2005 03:58:03 +0000 dori Just ten days ago, Dean wrote here about Acid2:

there has been no officially released browser that passes the test

I’m thrilled to say that that’s no longer the case — we have a winner!

With today’s release of Mac OS X 10.4.3, Apple’s Safari RSS (version 2.0.2/416.12) is the first (publicly-released, non-beta, non-preview) browser to successfully pass the Acid2 test.

On behalf of the Web Standards Project, congratulations to everyone who contributed to Safari and WebKit, and thanks for the hard work! We look forward to the day when Safari isn’t the only browser that can make this claim.

]]> 0
Opera to Use acid2 Beyond the Desktop Sat, 18 Jun 2005 19:08:41 +0000 mollyeh Opera Software plans to use the acid2 test not only to improve implementation and correct bugs within the desktop browser, but then do so for its mobile browsers, too.

Jon S. von Tetzchner, co-founder and CEO of Opera Software, writes:

“When our rendering engine gets it right, you can expect to see the smiley face on handheld devices and home media terminals as well.”

Opera Software’s advancing influence in the mobile space means a very good future for the implementation of Web standards within mobile phones and related devices.

For more information on Opera’s progress with the acid2 test, please see the acid2 progress thread on the My Opera Forums. While Opera isn’t doing a step-by-step report, they are posting their progress at least once a month along with a PNG image of the acid2 rendering as it looks at that point in their process.

]]> 0