Slashdot Log In
Opera 10 Alpha 1 Released, Aces Acid 3 Test
Posted by
timothy
on Thu Dec 04, 2008 04:13 PM
from the now-it-sees-all-the-spiders-and-tastes-color dept.
from the now-it-sees-all-the-spiders-and-tastes-color dept.
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."
Related Stories
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
Tom Wolfe Says ... (Score:2, Funny)
In-line spelling and grammar? (Score:5, Funny)
Perhaps the submitter could have benefitted from those.....
Re:In-line spelling and grammar? (Score:4, Interesting)
Parent
Meh.. (Score:4, Informative)
The acid test is important but what about important things for users..
Firefox had this years ago, seriously is this accurate, Opera just got these?
Re:Meh.. (Score:5, Informative)
Well, I guess it made up for it by having tabs, mouse gestures, speed dial, spatial navigation and dozens of other things before any of the other browsers.
Parent
Re: (Score:3, Insightful)
By that standard, Mosaic is the best browser ever, as it added inline images before most other browsers existed.
Re: (Score:3, Informative)
No. This analogy fails. It has nothing to do with Opera implementing stuff first, it has to do with them making up for lack of certain useful features by having their own useful features.
Besides which, spell check, mouse gestures, etc are hardly world-rocking features. It doesn't affect the user experience much if they aren't there.
Re: (Score:3, Informative)
'Besides which, ... mouse gestures, etc are hardly world-rocking features. It doesn't affect the user experience much if they aren't there.'
Indeed, until you start using them. They make the browsing experience better overall.
Re:Meh.. (Score:5, Interesting)
Parent
Re:Meh.. (Score:4, Informative)
I'll second that. Literally the very first thing I do after running Opera the first time after I install it is enable the mouse gestures (which happens automatically the first time I use one, which I do the first time I open a new page).
The mouse gestures in Opera, combined with the address bar search shortcuts, make Opera the fastest browser for me to use.
The fact that they keep releasing new versions before I've even had a chance to really put the previous one through all of its paces is equally impressive.
I've never missed auto-updates in Opera. It sort of annoys me with Firefox when I run Firefox and before it opens it installs a bunch of updates, including updates to plugins, then asks me if I want to keep using the plugins, then destroys the previous session I was going to load and shows me a page telling me that Firefox was just updated. It's nice that I'm always running the latest version of Firefox, but I don't always *need* to run the latest version, and I don't really like seeing that process as often as I do.
I could also harp on the memory usage with Firefox, but not only is that discussion out of place here, but it's been really difficult to find the reason why my version of Firefox sucks up all available RAM and other people I'm talking to running the same plugins (Firebug, AdBlock, Forecastfox) on the same sites don't see that. It doesn't change the fact that Firefox uses a ton of RAM, but it's hard to place the blame when it's not repeatable. But for reference, right now Firefox is using 344MB RAM, 397MB virtual with only 27 mins of CPU time. It has 2 tabs open to the same website. Opera is currently using 224MB RAM, 297MB virtual with 10 tabs open (including the same 2 as Firefox), with a total of 13 *hours* of CPU time compared to Firefox's 27 minutes (I already restarted Firefox once today; I think I restarted Opera a week or two ago). Again, it's hard to find the reason why Firefox uses so much RAM, but that doesn't change the fact that it does.
So anyway, yeah, mouse gestures rock!
Parent
Re: (Score:3, Interesting)
Re:Meh.. (Score:5, Funny)
Same here dude. It's awesome for browsing porn, plus the fact if you gesture forward (with the mouse, ahem) on a page of thumbnails it will cycle through the linked images.
I actually emailed Opera after an all night drunken 'test' session to tell them how awesome mouse gestures were and they sent me a t-shirt and a note of thanks. Obviously I told them I was cycling through hubble deep field pictures and not some hubba hubba deep feel pics.
Parent
Re: (Score:3)
I will never go back to a browser without mouse gestures.
Interesting. I'm just the opposite. The first thing I install for a browser is Vimperator [mozdev.org] so I don't have to use the mouse.
Re: (Score:3, Interesting)
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.
Re: (Score:2)
Competition is almost invariably a good thing for users, but in the case of web browsers, all it does is force the developers to add countless new "features" to "stay ahead of the competition" instead of spending that time making it do the things it already does the way it should.
Re:Meh.. (Score:5, Insightful)
Competition is almost invariably a good thing for users, but in the case of web browsers, all it does is force the developers to add countless new "features" to "stay ahead of the competition" instead of spending that time making it do the things it already does the way it should.
Like passing the ACID test? Like giving you a start page that's ridiculously useful? Like making tabbed browsing work? Like making sure that everything runs in its own process?
What exactly would you like to see the browser do better? It seems to me that they're refining things faster than they're adding features.
Parent
Re: (Score:3, Informative)
I don't care about standards at all, just one company's interpretation of them.
It's not the interpretation of one company. Do you know what W3C stands for? World Wide Web Consortium. Do you know what consortium means? "An association of companies for some definite purpose."
Yes, that means that people from Microsoft's Internet Explorer, Apples' Safari, Mozilla's Firefox, and Opera's Opera all take part in it. Many of the features that are introduced and later get standardized start as propriety features of one browser. Examples are the rounded CSS borders in Mozilla, Text field r
Re:Meh.. (Score:5, Informative)
Parent
Re: (Score:3, Insightful)
Re: (Score:3, Insightful)
Actually, as AVee mentionedyou can do this easily:
F12
Site Preferences
Scripting tab
un-tick Enable Javascript
"It's not where Firefox put it, and I can't install the plugins I know and love... Forget this 'trying new things' crap. Now to post ignorantly on slashdot!"
Behind the times? (Score:5, Funny)
Other features include a spell checker and auto updating.
Firefox had this years ago, seriously is this accurate, Opera just got these?
So Opera is a little behind the times...
Personally I can't wait until they get around to implementing horrendous security holes [slashdot.org] as a subset of its features!
Parent
Re:Behind the times? (Score:4, Funny)
Parent
Re:Behind the times? (Score:5, Interesting)
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.
Parent
Re: (Score:2, Insightful)
Firefox had this years ago, seriously is this accurate, Opera just got these?
Funny, considering most other browser alway feel like an old version of opera to me. Especially Firefox.
Honestly the only thing Firefox has going for it over opera is the plugins. Which I dont entirely trust.
Re: (Score:2)
Right, those are important features for sure, (arguably two of the most important), but to classify Opera has being "behind the times" as far as feature sets is inaccurate at best.
Re: (Score:2)
It's a good thing I never said "behind the times" then isn't it?
Re:Meh.. (Score:5, Interesting)
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.
Parent
Re: (Score:2, Informative)
Different software packages have different features? Details at 11!
Opera's had spell checking through ASpell for a long time. The new inline spell checking (as Firefox has had) is indeed a huge improvement.
Opera also has had a half-assed auto-updater for a long time. It would automatically and silently patch its local JavaScript (used for site compatibility fixes), but when a new rev appeared, it would merely direct the user to the
Re: (Score:2, Informative)
Firefox had this years ago, seriously is this accurate, Opera just got these?
This being Slashdot, I'm sure you'll be amazed to learn that no, it's not true!
I'm using Opera 9.62 right now. It has a spell checker, which wants to turn Slashdot into "Slashed" and doesn't like the word "Firefox."
It has an automatic update checker. It doesn't automatically download and apply the update for you, but it'll tell you when a new update is available and send you straight to the download page which is close enough in my book.
Both Opera and Firefox have a "Check for Updates" menu item in the "Hel
Re:Meh.. (Score:5, Insightful)
Firefox had this years ago, seriously is this accurate, Opera just got these?
Now you know how Opera users feel every single time there's a FireFox upgrade story.
Parent
Re: (Score:3, Informative)
Every Cocoa application gets spelling and grammatical checking for free on OS X. Having to include it at the application level does seem rather ridiculous.
Re:Meh.. (Score:4, Informative)
No. If you have Opera 9.x and Aspell installed right click on any text area and you'll see "Check Spelling" as an option.
http://www.opera.com/browser/tutorials/spellcheck/index.dml [opera.com]
Parent
Yes, but... (Score:3, Interesting)
...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.
Acid is just a dick size comparison anyway... (Score:5, Insightful)
From a user's perspective: Yes, it's cool to pass the Acid tests, but unless one of my favourite websites breaks in Firefox (or IE, for the less geeky among us), I really won't care.
From a developer's perspective: Until the really atrocious browsers (*cough*IE*cough*) get up to standard, developers will continue to have headaches coding for cross-browser compatibility anyway. Currently, you have to test for "IE" and "everything else" (ok, so you need to test in all the non-IE browsers for completeness' sake, but if it works in one of them it's very likely going to work in all of them).
Re: (Score:2)
*Yes, MS have lost a little weight recently, haven't they?
Re:Acid is just a dick size comparison anyway... (Score:5, Insightful)
From a user's perspective: Yes, it's cool to pass the Acid tests, but unless one of my favourite websites breaks in Firefox (or IE, for the less geeky among us), I really won't care.
If both Firefox and Opera pass the Acid tests, then there's a very good chance that your favorite web sites won't break in either of them. Passing Acid3 is not a reason to switch to Opera. Passing Acid3 removes a reason why you might not want to switch. If you're perfectly happy with your current browser and have no other reasons to consider switching, feel free to ignore this announcement.
From a developer's perspective: Until the really atrocious browsers (*cough*IE*cough*) get up to standard, developers will continue to have headaches coding for cross-browser compatibility anyway. Currently, you have to test for "IE" and "everything else" (ok, so you need to test in all the non-IE browsers for completeness' sake, but if it works in one of them it's very likely going to work in all of them).
Internet Explorer 8 passes Acid2; Microsoft is definitely working on getting "up to standard". Neither IE nor Firefox pass Acid3 yet, but it's definitely a goal that Microsoft and Mozilla should be aiming for. The purpose of the Acid tests is to highlight areas where some browsers don't precisely adhere to W3C recommendations; if these issues can be corrected in the browsers, so that all browsers behave the same way, then developers' lives will become MUCH easier. Indeed, as you point out, the current situation is that you only really have to test for IE and "everything else"; this is a dramatic improvement from the days of testing for IE on Windows and IE on Mac and Mozilla and Opera and Safari, and there would be significant differences between all of them. IE8 will mean a huge leap forward in cross-browser compatibility, and the Acid tests are one reason why.
Parent
Re: (Score:3, Insightful)
- IE6 usage will continue to decrease at a rate of 1-2% per month, putting it between 5-8% by the end of next year.
- IE7 will cont
Acid3 (Score:5, Interesting)
Re: (Score:3, Informative)
Re: (Score:3, Informative)
WebKit nightly, best of 6 runs (several failed at 98%):
Failed 0 tests.
Test 65 passed, but took 35ms (less than 30fps)
Total elapsed time: 1.18s
Opera 10 alpha:
Failed 0 tests.
Test 26 passed, but took 46ms (less than 30fps)
Test 69 passed, but took 27 attempts (less than perfect).
Total elapsed time: 0.62s
Not doing too badly. Test 69 failed on one of the WebKit runs too, but I guess a random nightly is gonna be worse than a scheduled alpha release.
Using it (Score:4)
I've been using it all day (Ubuntu 8.10, gcc4/qt4) and I've not encountered any major setbacks or bad renderings. There's some graphical distortions on the tab bar, but I have a feeling that's a purely cosmetic, chrome issue which could be resolved with a quick flick of the wrist.
Really, I think Opera is slowly becoming my browser of choice for day-to-day activities. It's just faster than Firefox or Safari or Chrome. I'd like to see it get the process separation abilities of Chrome and the extensibility of Firefox, and it would be awesome. I still use Firefox for development, though, because its market share is much, much higher and the tools are there (Firebug and Web Developer, plus Venkman, etc.).
However, the mail client and feed reader are still lackluster. Thunderbird does a better job of the former, Google Reader handles the latter better. If Opera could act as a frontend to Google Reader, I'd be a very, very happy man, and so would thousands of others who like desktop applications with web-based backends.
Items of note (Score:5, Informative)
Okay I gave the OS X alpha a spin. It does get 100 on the Acid3, but still doesn't manage smooth animation on my machine and probably not on the reference hardware. Javascript performance is behind compared to the latest Webkit and the Sunspider test. On my machine the Opera alpha is very slightly slower than the release version of Safari and about six times slower than the nightly Webkit with the new javascript improvements. The alpha does support some OS X system services, but still fails to use the default spelling and grammar checking, instead offering only a proprietary spellcheck that ignores my carefully trained dictionaries that work in most all of my other programs.
It's nice to see Opera is still in the game and trying, but it feels like they're still falling behind in the new, turbocharged browser race. Now if only IE would fix their flat tires and get back in the race.
CSS3 let-down (Score:2)
No border-radius? *sniff*
Is it specified in some stupid way like Mozilla & Webkit do it?
Still no local storage (Score:2, Interesting)
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.
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 compare
Re: (Score:3, Interesting)
No big improvement in their Javascript engine either.
It has much better performance in a Sunspider test than Opera 9.6x.
But nowadays they seem to fall behing other browsers
It's not feature complete, the website hint at more coming especially sometime during january 2009. Also, this summary and many comments here are missing out on major feature additions like SVG font and web font support, and the CSS improvements. Too much focus, as usual IMHO, is given on Acid3 scores.
Oh, please no, not "rich text" (Score:3)
Nested tabs please! (Score:3, Interesting)
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 [opera.com]
Acid3 != Standards Compliance (Score:5, Interesting)
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/ [nextapp.com]
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 [opera.com] 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.
Re:Acid3 != Standards Compliance (Score:4, Interesting)
That looks like a corner case situation to me. Maybe you would do better by not inflating the importance of bugs you report? :)
I strongly disagree. It breaks valid, commonly-used layouts and is quite difficult to workaround.
The example case is as simplified as possible to demonstrate the bug. I too don't think the example scenario will be hit very often. I think most people use the lower-right corner handle rather than bottom/top handles to resize a window, or simply use the maximize function. I used this example because it easily illustrates the issue.
The underlying problem however seems to come up quite often in my experience. Working around it has proven between difficult and impossible because all height data in the browser is incorrect (not current). It appears height data is not recalculated until the browser is *horizontally* resized.
There's quite a bit more information in that my.opera.com thread if you're interested.
Parent
Re: (Score:2)