Working together for standards The Web Standards Project


Acid2 and Opera 9 Clarifications: Yes, Opera 9 Passes the Test

By Molly E. Holzschlag | July 20th, 2006 | Filed in Action, ACID2, General

There’s been a bit of confusion over the Acid2 test and Opera 9 results. Ian Hickson has provided WaSP with the following clarifications about the Acid2 test and how things should behave. Hopefully, this insight will serve to clarify why some people are reporting issues in Opera 9 compliance.

Skip to comment form

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.”

Your Replies

#1 On July 20th, 2006 9:53 pm Jo 'Mangee' replied:

“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.”

The eyes do say error, but the text showing it is red on a red background.

So i’m confused, “It’s a Bug” means a bug with Opera or with the ACID2 test?

-Jo.

#2 On July 21st, 2006 4:20 am Axel Siebert replied:

What’s up with point 2? Everything from “becomes jagged” onwards is actually copied from point 6, and what should really be there instead is missing…

#3 On July 21st, 2006 2:56 pm Ian Hickson replied:

“It’s a bug” means it’s a bug in Opera.

Point 2 got corrupted due to copy-and-paste issues. It should read “2. The image changes when you resize the window such that the text in the paragraph at the very top of the page wraps: Not a standards compliance issue. It could be considered a user interface bug, but it is not a standards bug. (It’s could be a UI bug because if you’re at a fragment identifier and you resize
the window, the page should arguably remain at that fragment identifier. As far as I know, all browsers have this “bug”.)”

#4 On July 23rd, 2006 3:13 pm Nicolas Mendoza replied:

You also forgot to mention:

1. Adding User CSS files make ACID2 not render properly, for instance a css file like:

* { display: none; }

2. If you add a User JS file, like the ones you can get at http://userjs.org you might end up making Acid2 render wrong. For instance if you add a User JS file looking like this:

window.onload = function() { document.body.innerHTML = “”; }

3. If you execute some javascript on the page manually. For instance pasting this

javascript:document.body.innerHTML = “”;

in the addressbar of the tab currently displaying the Acid2 page will break it.

Of course all this examples are just nonsense just like some of the other points mentioned. The fact that Acid2 renders wrong in special view modes made to make up for badly designed pages (pages not made for small screens, devices, big screens, visually impaired etc.) has little to do with passing the Acid2 test IMHO.

#5 On July 25th, 2006 9:05 am khurram replied:

getting some wrapping issue bugs

http://megasolutions.net

#6 On August 1st, 2006 3:52 am Radomir Dopieralski replied:

If changing the preferences breaks the broswer (makes it not compliant to standards), then why the preferences are changeable in the first place? I’m especially concerned with point 5, since I fail to see how this should unevitably break anything.

#7 On August 2nd, 2006 12:36 am Kevin McGladdery replied:

I would suggest that changing preferences doesn’t change standards compliance, but since user preferences can be controlled by user style sheets, when rules in a user style sheet override the CSS in the test, you’re going to get a different result, just like any other CSS styled document you open.

If I tell Opera to display all text in red and at three times the normal size, it’s going to alter the appearance of any page, Acid2 test included.

Return to top

Post a Reply

Personal Information

Reply guidelines: Basic XHTML (a href, abbr, blockquote, cite, strong, em) is allowed. Line breaks and paragraphs are automatically generated. WaSP reserves the right to edit or delete off-topic or inappropriate replies.

Your Reply

All of the entries posted in WaSP Buzz express the opinions of their individual authors. They do not necessarily reflect the plans or positions of the Web Standards Project as a group.

This site is valid XHTML 1.0 Strict, CSS | Get Buzz via RSS or Atom | Colophon | Legal