Opera 9.0 Fully Passes ACID2 Test
Posted by
CmdrTaco
on Sun Mar 12, 2006 10:06 AM
from the both-users-celebrate dept.
from the both-users-celebrate dept.
Rytis writes "Opera has just become the second browser after Safari to be able to pass completely the famous ACID2 test. Mark Wilton-Jones is running a little article on the history of the Opera and ACID tests. Of course, it includes a screenshot of Opera 9 showing the nice happy face saying "Hello world!"."
Related Stories
[+]
First Look At the ACID3 Browser Test 104 comments
ddanier writes "Now that all major browsers have mastered the ACID2 test (at least in some preview versions), work on ACID3 has begun. The new test will focus on ECMAScript, DOM Level 3, Media Queries, and data: URLs. 100 tests will be put into functions each returning either true or false depending on the result of the test. The current preview of ACID3 is still missing 16 tests."
This discussion has been archived.
No new comments can be posted.
Opera 9.0 Fully Passes ACID2 Test
|
Log In/Create an Account
| Top
| 418 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Konqueror passed 2nd (Score:4, Informative)
Info here [kdedevelopers.org].
Re:Konqueror passed 2nd (Score:5, Informative)
"Opera 9 (get the weekly build) now passes the Acid 2 test, making it the second browser to do so. And yes, I can count. Safari passed first, and Opera is second. Konqueror and iCab almost pass (and claim to pass), but they both fail to apply one of the styles required by the test..."
Re:Konqueror passed 2nd (Score:5, Interesting)
Re:Konqueror passed 2nd (Score:5, Informative)
Re:Konqueror passed 2nd (Score:5, Insightful)
From your link:
"I want to be clear that our intent is to build a platform that fully complies with the appropriate web standards, in particular CSS 2 ( 2.1, once it's been Recommended)."
Its not really paraphrasing when you make up ideas. That's called "reading between the lines", and you didn't even do that.
Actually Firefox do care a lot about Acid2 (Score:5, Informative)
It's just such a complex problem to tuckle that it seems to me (as a sideline spectactor) to be stupid to block the entire Firefox train just for it. They are working on it.
Re:Konqueror passed 2nd (Score:4, Informative)
--
onedotzero
thedigitalfeed.co.uk [thedigitalfeed.co.uk]
Re:Konqueror passed 2nd (Score:5, Informative)
That's not a bug, that's exactly what is supposed to happen when you scroll the page. From the technical guide [webstandards.org]:
Re:Konqueror passed 2nd (Score:5, Informative)
From what I've read here, Konquerer still shows the scroll bar, and Opera doesn't have the scalp come off when you scroll.
So, Safari passes, everything else still got some work?
At least they all pass a hundred times better than IE...
Re:Konqueror passed 2nd (Score:5, Insightful)
Who got there first also isn't important, we just need all browsers to get there.
Re:Konqueror passed 2nd (Score:5, Insightful)
> of course, but in the real world practically nobody is going to be using CSS in that way.
It's not purely academic, it's eminently practical - as the site explains, all of the features are unlikely to be used on the same page, but designers rely on each one of them to work correctly at some point, and have been requesting proper support for years so their pages look consistently good on all browsers.
It claims to but fails (Score:5, Informative)
"Konqueror and iCab almost pass (and claim to pass), but they both fail to apply one of the styles required by the test, and as a result they display a scrollbar even though they shouldn't (the Acid 2 guide neglects to mention this style, but see the source code for the test itself):
html {
Re:Konqueror passed 2nd (Score:5, Informative)
Safari is an OSS project too.
No it isn't, WebKit, the rendering engine Safari uses, is an open source project. Safari itself is very much closed source.
WebKit matters, not the Safari frontend (Score:4, Insightful)
In a discussion about the Acid2 test, you claim that Safari isn't free software:
But the frontend code isn't very relevant to this discussion. Safari passes Acid2 if and only if [wikipedia.org] WebKit passes Acid2. Or do you claim that Apple maintains a private WebKit tree with patches that don't get released to the public and that one or more of the private patches is required for WebKit to pass Acid2?Re:WebKit matters, not the Safari frontend (Score:5, Interesting)
Not tested any others but I'm sure Xylescope, TextMate and OmniBrowser all use WebKit too.
Re:Konqueror passed 2nd (Score:5, Interesting)
But seriously, who gives a shit who came first, second or whatever; I think the important thing is that browser developers are obviously making an effort to ensure stricter standards compliance. I assume someone must be working on this for Firefox, so does anybody know when we can expect to see Firefox pass Acid2 as well?
Re:Konqueror passed 2nd (Score:4, Informative)
Track Gecko progress here. Including screenshots.
Link as plain text due to
ACID passed, real world? (Score:5, Insightful)
Re:ACID passed, real world? (Score:5, Informative)
The problems with Opera's JS arise in three situations:
1) The site specifically blocks out Opera due to scripts 5-6 years old, but happily copypasted throughout the web project by brainless "web designers". Or server-side sniffing, like Yahoo did and still does, AFAIK.
See here for example, one that I found just a few minutes ago when informing myself of the latest and greatest Bollywood hit: http://www.rangdebasanti.net/ [rangdebasanti.net]
Their JS code contains this:
Use Proxomitron or Opera's cloaking techniques to get rid of the "Opera" part in UA string, and what do you know, the site works perfectly!
2) The site doesn't block Opera per se, but exhibits "if IE or Netscape" behaviour. Of course Firefox deals with those, as it descends from Netscape. Opera doesn't, and Opera is not IE, either, so it end up in no man's land...
3) The site has JS errors, and Opera is pretty strict when parsing JS, more so than Firefox or IE.
Honestly, Opera does not have any JS issues. None whatsoever. It's brainless webmonkeys who have issues with their JavaScript.
Re:ACID passed, real world? (Score:5, Informative)
Moreover, it's a fallacy to expect a browser to "work in all situations". I'm sure there are plenty of real-world situations where Firefox fails as well, and where Safari were to succeed in it's place. It's tests like ACID2 that determine a browsers capability to handle all situations.
The problem Safari is having with Exchange is very likely due to poor coding. Considering it's from Microsoft (you said Exchange web interface, right?), I'm sure Microsoft implemented a slew of hacks to have Firefox compliance (Microsoft is well known for improper web developing practices, to put it lightly).
Re:ACID passed, real world? (Score:4, Insightful)
I haven't found that. Firefox is ahead on some things and behind on others. For example, Safari supports DOM 2 mutation events, but Firefox doesn't.
You're joking, right? Internet Explorer's DOM support is prone to memory leaks and doesn't support basic things like event handling. I'd rephrase your statement as:
"As Internet Explorer has shown, having the largest market share is much more important than supporting most of the CSS or DOM specifications, because that way the web developers work for you, not the other way around."
I think that a lot of people have blind spots, where they are completely unaware of many parts of the specifications, because they don't work in Internet Explorer or Firefox.
Re:ACID passed, real world? (Score:4, Informative)
Re:ACID passed, real world? (Score:5, Informative)
It doesn't support event handling as defined by the DOM specifications. My comment is perfectly clear when you don't cut the quote off prematurely.
Referring to Internet Explorer's proprietary DHTML interface as a "DOM", while technically accurate, is misleading as in common use, the term "DOM" refers to the W3C specifications.
How about a little maturity?
a) No it doesn't, many Internet Explorer memory leaks [microsoft.com] are an artifact of the JScript engine being unable to refcount properly.
b) You implied that Internet Explorer had a "solid" DOM. That is not true regardless of the quality of Firefox's DOM. Internet Explorer's DOM doesn't get more "solid" if you distract people by talking about other browsers.
Re:ACID passed, real world? (Score:5, Informative)
First off that one hasn't been built, as I've seen IE manage to screw up royally too on sites claiming to work with IE, sometimes only with IE. The trouble with trying to match IE bug for bug is that you can't succeed as you can never duplicate the implementation exactly, you need to render pages wrong according to the standard, and worst of all it is never predictable. I really hate "trial-and-error" programming, and IE is the worst of the bunch.
In your case, you're trying to use MS generated HTML. I'm sure the fact that Firefox can render it is completely accidental and will be fixed in the next Exchange service pack. You can't expect a company that has a vested business interest in not playing nice, to play nice. The ACID2 test is an assurance that if I code to the standard, I will see none (or at least very few) rendering issues on any browser (except IE). That is very reassuring to people who think "OMG supporting five browsers, do I have to make 5x the number of hacks?" No, you don't. In fact, you'll code to one standard and fix hacks for one browser. Which is actually better than to code to zero standards and fix hacks for one browser...
Safari hates malformed pages (Score:5, Interesting)
There are a lot of crappy pages out there. If a page doesn't make it through the HTML validator why should anyone expect a browser to render it? Are your pages at work valid? What's the point of standards-compliant rendering engines if they all allow exceptions to the standard to be rendered?
A lot of times Safari won't render big chunks of web pages because of malformed markup [mozillazine.org]. Dave Hyatt (rightly, I believe) doesn't want to spend lots of coding effort dealing with error recovery when parsing sloppy web pages. Browsers like MSIE and Netscape (pre-Mozilla) are too permissive and have allowed people to get away with downright bad HTML.
That said, the Safari Compatibility Hit List [opendarwin.org] was recently created, to either fix Safari compatibility problems or to encourage sites to fix their markup.
Tweaked (Score:5, Interesting)
Re:Tweaked (Score:4, Interesting)
The reason Opera is "victimised" by older scripts is due to the ridiculous decision of that company to add code stubs for functions it did not actually support (I remember when it had document.getElementById(), which always returned null - that's why many scripts look for the Opera string, and block it).
Get the weekly (Score:1, Informative)
ICab and Konquerer don't pass (Score:1, Redundant)
Good news (Score:4, Insightful)
A big well done to the Opera team. Safari passed the test in November last year, and hopefully Firefox will pass soon as well. Increased standards compliace is a Good Thing(tm) for users and webmasters alike. If the minority browsers continue to push standards (which the tech-savvy webmasters follow) it will push IE into improving its own rendering engine. Although even their unreleased version seems to be a bit behind the times...
From TFA: It is somewhat worrying that IE 6 renders Acid 2 very similarly to Opera 3.6, and the hyped IE 7 renders it very similarly to Opera 4.
'Somewhat worrying' indeed. I know people (of the pretty-damn-computer-literate variety) that won't switch from IE6 because it "works fine for them". I'm sure they know about the vulnerabilities [now that Symantec says so, it must be official!], the rendering issues and speed*, but they are sticking to their guns. So the only way people like this will have their experience enhanced is by teams like Mozilla and Opera pushing the browser envelope and hoping IE take interest. Either that or some X factor that makes the alternative browser a 'killer app', rather than IE, which is an app killer. (I couldn't resist, sorry!)
Well done again to Opera. Webmasters everywhere are silently saying a big 'thank you'.
*Note: I am aware that some will say that IE 6 loads quicker/renders quicker than FF. I have found the two of comparable speed for light pages, and FF slightly faster for 'heavier' pages. Opera is faster than both of them. Draw your own conclusions, and install all three (or two if your run a non-Windows OS). I found an old demo disc with IE 3 recently, and will be trying that out.
I like how... (Score:5, Insightful)
Internet Explorer getting better (Score:5, Funny)
Re:Internet Explorer getting better (Score:5, Informative)
Re:Internet Explorer getting better (Score:4, Funny)
IE 7, the Hannibal of web standards?
who was first after safari? (Score:3, Insightful)
Second browser after Safari? Which was the first after Safari to do it? Oh, you mean the second browser, after Safari...It's amazing what commas can do. Learn to use them.
An ACID test giving a smiley? (Score:5, Funny)
Re:An ACID test giving a smiley? (Score:5, Funny)
See how your browser fares... (Score:5, Informative)
Lynx doesn't pass... (Score:5, Funny)
When Will IE Pass the Test? (Score:1)
Who the hell cares (Score:1, Interesting)
Yeah, but... (Score:5, Interesting)
Re:Yeah, but... (Score:5, Interesting)
For the curious - (Score:2, Interesting)
Also, It would appear that Opera 9 has just one thing wrong - the nose. It's not supposed to be blue, it's supposed to be black, as per the sample rendering here: http://webstandards.org/act/acid2/reference.html
Re:For the curious - (Score:5, Informative)
More elaborate history (Score:5, Informative)
There's a more useful history about it here [timaltman.com] (in reverse chronological order), describing what exactly the standard compliance problems were, and how they fixed them, starting with Opera 8.00.
And go to the Opera Desktop Team blog [opera.com] to download the actual build that works with this. However, note that this build should be treated like a Firefox nightly, and there may be some pretty serious rendering regressions, doing currently more damage to the layout engine than good from following the Acid2 test.
big deal (Score:3, Funny)
Not what I want (Score:2)
Pff, that's nothing! (Score:1)
I remember when I first tried the ACID Test (Score:1)
RIP Mitch Hedberg, we miss you
Webpage that only support compliant web browsers (Score:1)
ACID2: valid test or not? (Score:1)
On the introduction page [webstandards.org] they write:
Now these two messages seem completely contradictory to me. And especially if the second message which states that the CSS is invalid, is true, how can you expect browsers to render it correctly? If the CSS is invalid, than it seems to me it is completely undefinded how a browser should render this.
Can anybody enlighten me?
Re:ACID2: valid test or not? (Score:5, Insightful)
So the test is verifying conformance not only with treatment of valid CSS, but also correct treatment of invalid CSS, which is very important given that a significant part of compatibility problems between current web-browsers is caused by different behavior in the face of errors - whether they ignore it, stop parsing, try to render it anyway etc.
Why is it so hard to follow standards? (Score:2, Interesting)
Acid Test (Score:2)
Released? (Score:1)
I saw IE7 fail this on the CeBit today (Score:3, Informative)
I convinced one of them to open the ACID2 test in the IE7 (Google was blocked and he told me to use MSN Search, but I fired up Seekport). It was the worst rendering of the ACID2 I've ever seen. The entire screen was red, except for a few lines and dots here and there, and scrollbar in the nothing way over to the right.
Of course, the Microsoftie was quick to say, it's all only beta...
Cross-browser hacking sucks (Score:1)
Anyway, oftentimes when developing a site, if I make a page according to standards, and it works correctly in modern browsers (that is, not IE), I do not want to bend over backwards to make it work in IE. So when people tell me that something is broken in IE, I want to tell them that their browser is broken and that they should download a browser like Firefox or Opera or what have you. Obviously, this isn't a choice for many developers because many people still use IE, and many customers do not want to hear that they have to change browsers. What I want to know is, has anyone actually made a customer download a new browser because something that you or your company developed did not behave correctly in IE but behaved according to web standards? How successful were you in doing this? The reason I ask is that I always hear people proclaiming "standards!", or, "my browser passes Acid2!" but it doesn't seem of much use because I never hear of anyone actually forcing people to use any of these browsers that can understand up-to-date standards. I don't think we can make much progress in enforcing web standards without actually expecting standard-compliant web sites to render correctly, and alienating IE for as long as they are not compliant.
How Browsers Are Supposed to Handle Invalid CSS (Score:1, Informative)
Since a lot of people point to the fact that the Acid2 test contains invalid CSS I thought I'd point out that this was in fact intentional.
The reason why is described in the above link, CSS defines how a browser is supposed to behave when it finds invalid CSS.
Testing whether a piece of software behaves correctly when presented valid data is only half of bug-testing.
The other half is testing whether a piece of software behaves correctly when presented invalid data.
Acid2 covers both halves.
CSS is supposed to fail more gracefully than XML and XHTML and ignore only those parts that are incorrect.
Acid2 is annoying (Score:1)
I want to know... (Score:1)
ACID2 Test = crap (Score:1)
Note: some 827 people (rough estimate, contents may have settled during shipping) have written to point out that the CSS used in the test is invalid. This is deliberate, as a means of exposing the ability of user agents to handle invalid CSS properly.
That's it. Encourage developers to support invalid coding by designers. That's the way to encourage web standards!
Interesting-- Konqueror claims to be second also.. (Score:1)
Slashdotted (Score:1)
Re:*smack* (Score:2)
The important thing is who is there and who isn't. The order in which the browsers arrived at compliance is of no consequence to users of the browsers.
Re:Cool (Score:5, Insightful)
But I'm happy with Opera, be it for the faster responce I get on the same machine as I have Firefox installed on, the ability not to search for plug ins for whatever feature I need, 'it just works'
I just find Opera is faster at implementing standards, is more reliable with IE geared sites (don't like the fact, but I have to be pragmatic and deal with it as promoting interoperability is not what pays my bills), is more innovative (has important new features first and has them 'out of the box') and makes a good testing ground for my projects, and is all together very nice. And now it's free (as in beer).
Firefox is good. Opera is good too. Different priorities for different users, I don't have access to source code or the ability to contribute in the same way, but for me I'm fine with that. Both are far superior to IE's features, security and map for an interoperable internet in the future. Nuff said.
Re:iCab (Score:2)
"Opera 9 (get the weekly build) now passes the Acid 2 test, making it the second browser to do so. And yes, I can count. Safari passed first, and Opera is second. Konqueror and iCab almost pass (and claim to pass), but they both fail to apply one of the styles required by the test..."
Re:*smack* (Score:3, Informative)
Re:iCab (Score:1, Informative)
Safari did it first, then iCab, then Konqueror, and now Opera. See http://dean.edwards.name/weblog/2005/04/acid2-sp/ [edwards.name] . This order is not the "release" order, but when an alpha/beta/nightly passed the test, and the developer(s) told us.
If we consider released versions, I'm not sure what order we get, but I believe only Safari and Konqueror have released the compliant versions yet.
Re:iCab (Score:3, Informative)
That makes Opera the 4th browser to render Acid2 correctly.
This page has a bit of info on it, http://dean.edwards.name/weblog/2005/04/acid2-sp/ [edwards.name]
Safari, iCab, and Konqueror aren't for Windows (Score:5, Interesting)
It also makes Opera the first publicly available web browser that renders the Acid2 page correctly under the Microsoft Windows operating system. This is important if you don't want to have to re-buy your PC (in switching to Mac OS X, which runs only on Apple hardware) or your peripherals (in switching to Linux, where SANE still doesn't support my flatbed scanner [sane-project.org]). Or is Konqueror for Cygwin/X considered stable yet?
Re:Second browser? (Score:3, Informative)
Re:Ah opera... (Score:2)
Re:Ah opera... (Score:2)
No it hasn't... (Score:5, Informative)
Re:Ah opera... (Score:2, Insightful)
Re:Ah opera... (Score:5, Insightful)
Then maybe you should stop making websites, because people like you are the problem.
They're "only a guideline" in that the FBI won't knock on your door if you don't follow the standards. And oh yeah, a lot of browsers will accept your sloppy coding and "render it fine." However, if you want a world where all browsers render all content in the same way, that can't be accomplished by the developing team of any browser. That can only be accomplished by developing and following standards. So, you blame the browser when they don't follow them, and you blame the web developer when he doesn't follow them.
I'm fine with browsers who want to go the extra mile and have non-standard code render correctly, as long as they don't sacrifice proper rendering of the standard code to do it. That doesn't excuse you coding incorrectly, though.
Re:Ah opera... (Score:5, Informative)
Well, it's great that you do all that work to consider your visitors. What I was referring to was your comment that following standards isn't really that important, it's just a guideline. That train of thought is part of the problem.
Think of a world where every browser renders everything in the standard correctly. Suddenly, your job is easier. In order to make sure that your web page renders correctly for the visitors using IE, Firefox, Safari, Opera, Konqueror, whatever, you don't need to actually test it with each one of those browsers. You just need to make sure your site follows the standards, and the rest "just works". If you skip out on things because "they're dumb," well, you may think you're right, but why do you expect browser developers to share your opinion?
You'll see 12 ridiculous errorsDepends on your definition of ridiculous. You wouldn't expect c code that doesn't have syntax exactly right to compile, so why do you expect html syntax that isn't exactly right to render correctly?
from things like > characters whose position it disagrees with
I didn't find that. I found error #3. It's not complaining about the position of the character, it's complaining that you placed that tag inside your unordered list, but not within a list item tag. I checked the source code and you have:
<ul id="utabs">
<a href="?page1"><<</a>
If it's part of the unordered list, it should be inside a <li> tag. If you don't want for that to appear the same as the other list items, you should give it a class attribute and handle it in your css (there are other correct ways of handling it too, if you don't like that for some reason).
That and a childish remark about my html tag which was funny for the 1.3 seconds I spent writing the top line...
It wasn't your remark that it complained about. It complained about your type. That's not how you specify 4.01. From a W3C page, there's this example, using SGML to do what you want (for strict 4.01).:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
Heck...you should be fine just skipping that altogether. Close your html tag, and don't put the type thing.
errors that don't tell me anything useful or constructive at all
The validator doesn't tell you how to fix it, just that it found something wrong. However,
a wikipedia url I pasted, which the validator decided to parse and rate
For that error, the validator told you exactly what was wrong...in bold. "The most common cause of this error is unencoded ampersands in URLs". I've actually noticed that in other places in your html code for that page, stuff that I expected the validator to complain about, but it didn't.
In html, if you want to have a "<" or ">" that is not part of a tag, you use a code. you type in "<" for < and ">" for >. If you want to type "&", you type "&" Replace the & in that url, and it'll pass. You should replace the <'s I mentioned in error #3 with the correct codes too, even if the validator doesn't complain about it.
I'm not trying to be a bastard about it. I hope my comments help you understand the validator better, and see that it's not so useless as you've come to believe. It's great that you've been putting effort to make sure your visitors get the best experience they can on your site, and I hope you'll keep doing so.
Re:This does NOT pass Acid 2 (Score:5, Informative)
The nose changes color when you mouseover it. Even in the mess that is Firefox's rendering of the page [webstandards.org] hovering your mouse over the face causes the nose to change colour from black to blue.
I guess that's something they really should specify in the reference diagram, but it's still a pass for Opera 9.
Re:This does NOT pass Acid 2 (Score:5, Interesting)
Re:Uh... (Score:1)
Seems to be a CSS issue? (Score:1)
When I come across badly rendered pages, applying user stylesheets [opera.com] solves the problem most of the time.
Re:Ah opera... (Score:1)
I ran your page through the validator and got 80 errors. You expect this to render correctly?
Before you start throwing stones at the browser of your choice, make sure your page validates.
Re:CSS weirdness (Score:1)
The validator reports 47 errors on your page. Fix those first and then start working on why the page doesn't render properly.
Re:Ah opera... (Score:1)
The W3C validator shows 80 errors on your webpage. http://validator.w3.org/ [w3.org]
You could try fixing those first.
Re:And, on cue... (Score:3, Interesting)
Personally, I think the correct rendering of the ACID2 test is a blank page, or maybe an error message that says something like, "This is not a web page."
Re:Ah opera... (Score:1, Funny)
RTFA, Troll (Score:2)
I might have produced a testcase but... (Score:1)
While your page has HTML errors (like poorly nested tags) it's hard to know whether it is those very same HTML errors that are causing layout issues. More often than not it is, making people very reluctant to go to the effort of debugging a page until they are all fixed. When your markup validates you are far more likely to be able to pique people's interest that you have found a browser bug because it is one (or in this case 47) less thing to check.
If you DO manage to get that page to validate and still see the problem you might want to ask again though...