Opera 10 Alpha 1 Released, Aces Acid 3 Test
Khuffie writes "It seems that the upcoming version of Opera 10, of which the first Alpha has recently been released, has already passed the Acid 3 test with a 100/100. The only other rendering engine to have a complete score is WebKit, which can be seen in Google Chrome's nightly build. Opera 10 Alpha 1 will also finally include auto-updates, inline spell checking, and see some improvements to its built-in mail client, including much-requested rich text composition."
...is it smooth? I thought that was part of the criteria for passing the test, not just the 100/100 thing.
Still, congratulations to the Opera team. Now for Acid4, whenever that comes out.
Scoring 100/100 on the JavaScript subtests is only part of passing Acid3. A browser also has to render the page correctly (including the proper favicon) and complete each subtest within a certain amount of time. From reports in the Opera forums, it looks like Opera 10 still isn't passing the performance aspect of Acid3. I think Safari 4 is still the only browser to fully pass Acid3.
What a fool believes, he sees, no wise man has the power to reason away.
In my defense, I DID spell 'sign' right. It's not like the spell checker would have caught it...
Opera had spellcheck since about forever, just not one that would underline the incorrect words like Word does. And it also isn't nearly buggy enough to require frequent automatic updates, so clicking the occasional prompt once a new version is available (detected automatically) worked just fine.
However, I'm disappointed that they finally bent over and decided to include HTML mail.
It looks like it still doesn't implement any kind of local storage.
A feature that other browsers have for years, including IE since IE 5.5.
No big improvement in their Javascript engine either.
And Dragonfly is still way behind Firebug and Web Inspector. /., it's now the opposite.
Opera used to be great, it was ahead of time in the Mozilla Firebird days. But nowadays they seem to fall behing other browsers. Plus Opera is closed-source and there's even no NetBSD/OpenBSD/DragonflyBSD blob. Plus it used to be fast and light compared to other browsers, but according to recent stories published on
I was an Opera lover, but nowadays, I really see no point in using it over Firefox and Webkit.
{{.sig}}
My gp comment was just as relevant as your original post. Yes Firefox had spellcheck as an implemented feature for a longer time than Opera, but length of implementation is fairly irrelevant - both of them now have the feature and should be judged as such.
If you can't live without spellcheck in submission spaces in a browser (which I no longer can after using this feature in Firefox since implementation) I understand that was and should have been a determining factor. At this point and for reasons of that particular feature though, they should be judged on equal ground. Additionally and as I pointed out, another factor for a lot of people should be security. I personally am considering switching to Opera (or at least downloading / running side-by-side to Firefox) now that it has a much larger feature set and for the time being seems to be more secure.
I just think the argument of "but this already has those features" is an argument borne of fanboyism alone and the browser should be judged on full merits. Opera for that reason looks pretty good right now.
Well, back to rejecting software patent applications.
Only thing Opera is missing is something along the lines of "no script", its really disapointing they left this out.
I will never go back to a browser without mouse gestures. No other browser feature affected my user experience as much as that one. Not even tabs (but perhaps that's because I've often used a separate virtual desktop for the webbrowser).
I love Opera more than any other browser out there and use it all the time, but wake me up when it starts to support nested tabs. There was a post by a Firefox user not so long ago who mentioned such an addon. People are rightfully raving about this time saving feature (and similar addons).
Tabs are grouped hierarchially according to where they are opened from in the form of a tree, but they can be expanded if need be. Tab names can be fully seen (instead of just graphical icons), and a whole branch may be closed (e.g. a site + its sub pages). A massive space saver when you are working with loads of sites.
I posted a message on the Opera forum. One can but hope:
http://my.opera.com/community/forums/topic.dml?id=257296
Why OpalCalc is the best Windows calc
I can't tell if you're trying to criticize my spelling or not... :/
At any rate, I never felt a need for spell check. Chrome's spell check just annoys the piss out of me, because 99.9% of the time, it's wrong. I'm spelling something legitimately, but because it's not in the rather limited dictionary, it gets flagged. For the spelling on my posts, I guess I've always just been one who gives my post the once-over to make sure that there aren't errors.
"16MB (fuck off, MiB fascists)" - The Mighty Buzzard
Web-Kit is also the core for Safari. And it first passed Acid 3 Sept 25, 2008 in the nightly build of Safari.
http://webkit.org/blog/280/full-pass-of-acid-3/
Just tried it out, and of course it passes ACID3 as advertised. I still can't recommend this browser on the grounds that it can't correctly render absolutely positioned CSS elements, as demonstrated by the following code:
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>Resize your browser with the vertical handle!</title>
</head>
<body>
<div style="position:absolute;left:20px;right:20px;top:20px;bottom:20px;background-color:lime;">
<div style="position:absolute;left:20px;right:20px;top:20px;bottom:20px;background-color:red;">
</div>
</div>
</body>
</html>
Hosted version of the above:
http://echo.nextapp.com/content/test/operacss/
Opera 9.50, 9.60, and now 10.0alpha will not render the above properly if the browser is resized vertically. (9.27 and prior work perfectly) On the initial render, 9.5/9.6 and 10 do fine, but the moment one resizes the browser vertically (and NOT horizontally as well), things go awry. I reported this to their bug tracker six months ago, and posted a thread on their forums 2.5 months ago: http://my.opera.com/community/forums/topic.dml?id=250572 Have also mentioned it in their 9.6-about-to-be-released-post-non-working-sites thread.
This bug has additional consequences for AJAX applications that make use of on-screen measuring using offsetWidth/offsetHeight information. In such cases, even the initial rendering can be seriously flawed as offsetHeight returns incorrect values. (Note: offsetXXX properties are not part of a proper W3c standard, but are universally supported).
Apologize for the quasi-rant, but I just don't want to see another bug report about how our applications don't look right in a supposedly ACID3 compliant browser, thus indicating that the problem "MUST" be our fault. Please realize that passing ACID3, while a neat accomplishment and generally good thing, is far from a guarantee of standards compliance.
Try a clean profile, there might be something wrong with yours. I keep 99 days of history and even with 20+ tabs open in FF3.0.4 with 9 addons installed I'm only using 151MB on a 2GB XP SP2 machine.
There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
This is what I am getting: Opera 9.5: 76.7 Opera 9.62: 166 Opera 10a: 157 Chrome: 1801 Firefox: 132 The Webkit nightly keeps crashing on startup for me, but whoa. I had no idea these two browsers were so so so much faster than the rest.