Hello Opera 10.60
By Bruce Lawsonbrucelawson. Thursday, July 1, 2010 6:00:00 AM
We're very pleased to release Opera 10.60 for all platforms. Linux users will notice that we're skipping 10.5x Final, as we want to get all platforms in step again.
Features
I don't know about you, but I like having some new things to play with! We've got some speed, some HTML5 and some "HTML5" for you.
Speed

When it was released back in March, Opera 10.50 was the fastest browser on the planet — now with Opera 10.60, we've cranked the dials up to 11 and set the controls for the heart of the sun, increasing our JavaScript engine's performance to make it up to 50% faster than the previous version.
Geolocation
Allowing sites access to your location can enhance their usability and utility, and this feature comes to Opera 10.60. As an example, we've created this live download map of Opera 10.60. For a closer look at this technology see Shwetank's article How to use the W3C Geolocation API.
A note on privacy: when a site requests Geolocation information, the browser will alert you and ask for permission. You can grant it or deny it, and optionally have the browser remember your choice for that site on subsequent visits.
Geolocation works best on desktop computers using WiFi. This is because the location services provider (Google, in the case of Opera 10.60) compares the information about WiFi networks near you with its central database of WiFi hotspots and locations to find out where you are. Opera 10.60 has an option to periodically send such information to our service provider; this is off by default in Opera 10.60 in order to protect your privacy and conserve your bandwidth. If you wish to enable it and help improve the database, turn on the Collect location data in background option in opera:config#Geolocation.
You might also be interested in Privacy of Geolocation Implementations, a position paper by Marcos Caceres for the W3C Workshop on Privacy for Advanced Web APIs.
HTML5 AppCache for Offline Applications
HTML5 allows developers to code offline applications: in-browser applications so that they continue working when an internet connection is unavailable. This is as useful for a London businesswoman working on a train as it goes through a tunnel as for an Indian student working on a laptop during a power outage. Read our tutorial Running your web applications offline with HTML5 AppCache.
AppCache further blurs the difference between Web and desktop applications, and at Opera we're very excited about this. Our developer environment Opera Dragonfly uses of AppCache so it can work offline too. (Read more about Opera Dragonfly using HTML5 AppCache.)
WebM video
Opera 10.60 is the first browser to ship with support for WebM video, the new video codec open-sourced by Google as a very high quality codec for delivering video content over the Web (including streaming video) without the royalties than encumber its competitors. YouTube is converting all its videos to WebM. It's the future of video over the Web; as Håkon Wium Lie, our Chief Technology Officer and co-inventor of CSS, said:
WebM will join the list of open and freely usable Web formats, and video will finally become a first-class citizen of the Web.
Web Workers
We've begun our work to support Web Workers. Web Workers allow your JavaScript to delegate tasks to other processes that run in parallel, so your main script can do the exciting stuff while the Web Worker sits in the corner doing heavy computations without slowing the main script down. Our very own Daniel Davis has written a fun tutorial Web Workers rise up!
You might not notice significant differences in timings in Opera with Web Workers running (check our Web Workers speed test in Opera 10.60 and other browsers). This is because we've long built our JavaScript engine so that it doesn't slow down too much even while doing heavy lifting (which is why we have the fastest JavaScript engine in the world). Opera is a single-threaded application currently, so Web Workers don't speed it up that much. As we develop a multithreaded version of Opera (for platforms that can support that—not every platform can) you'll notice greater speed differences between apps that use Workers and those that don't.
Vendor Prefixed CSS
Opera 10.60 supports a small number of CSS properties with vendor prefixes. See -o- vendor prefixed CSS supported in Opera 10.50 and 10.60.Bugs
We sincerely hope there aren't any, but it's almost certain that there are so, if you find a bug please help us squash it using our bug reporting wizard.

1 2 Next »
docThe-Doc # Thursday, July 1, 2010 6:21:33 AM
DavidSchalandra # Thursday, July 1, 2010 7:43:28 AM
So what will be the next step? WebGL would be really awesome...
Anonymous # Thursday, July 1, 2010 8:07:38 AM
DamirLukina # Thursday, July 1, 2010 9:38:55 AM
Anonymous # Thursday, July 1, 2010 9:45:49 AM
berend ytsmaytsmabeer # Thursday, July 1, 2010 9:46:41 AM
Anonymous # Thursday, July 1, 2010 9:47:24 AM
Kamen Naydenovpau4o # Thursday, July 1, 2010 9:59:55 AM
Anonymous # Thursday, July 1, 2010 10:00:29 AM
Matthew Wilcoxsonmwilco # Thursday, July 1, 2010 10:05:01 AM
Particularly liking HTML5 improvements and geolocation - what a great combination.
NutzShells # Thursday, July 1, 2010 10:43:15 AM
Daniel Ziltenerzilti # Thursday, July 1, 2010 10:52:59 AM
Bruce Lawsonbrucelawson # Thursday, July 1, 2010 10:56:57 AM
Thanks everyone for your good wishes!
Anonymous # Thursday, July 1, 2010 10:58:13 AM
Mayur S. KhuntMayurSK # Thursday, July 1, 2010 11:57:28 AM
Charles SchlossChas4 # Thursday, July 1, 2010 12:50:44 PM
tonykusumamastercountry # Thursday, July 1, 2010 1:07:04 PM
M Haidar Hmhaidarhanif # Thursday, July 1, 2010 1:07:15 PM
berend ytsmaytsmabeer # Thursday, July 1, 2010 1:09:37 PM
Originally posted by mhaidarhanif:
Chrome 6 isn't stable yet. Compare stable against stable
M Haidar Hmhaidarhanif # Thursday, July 1, 2010 1:13:39 PM
Originally posted by ytsmabeer:
But at least, just for comparison.
Or maybe just put a snippet over there.
Zi Bin Cheahzibin # Thursday, July 1, 2010 1:23:48 PM
Originally posted by mhaidarhanif:
We wanted to compare release to release. I believe Chrome 6 is still a dev release.
Charles SchlossChas4 # Thursday, July 1, 2010 1:45:31 PM
Originally posted by zibin:
Metal Warriormetalbrother # Thursday, July 1, 2010 1:47:45 PM
Thanks opera,
v-love # Thursday, July 1, 2010 2:33:59 PM
Kai OckendorfOckendorf # Thursday, July 1, 2010 2:44:14 PM
raisinglight # Thursday, July 1, 2010 6:09:31 PM
please fix this because i don't want to use IE8 because it is evil and it kills mongolian babies everytime you click
mlouis # Thursday, July 1, 2010 7:13:14 PM
But still a very good release, thank you for working as well for Linux
IKoke # Thursday, July 1, 2010 10:25:33 PM
Zi Bin Cheahzibin # Friday, July 2, 2010 6:09:16 AM
Originally posted by raisinglight:
Hi Raisinglight, thanks for bringing this issue up, upon testing it worked for me.
If it still fails for you, it'd be great if you can send a bug report to https://bugs.opera.com/wizard/
Thanks again!
Kimmo Jaskarikimmoj # Friday, July 2, 2010 8:53:38 AM
Badtz Maru # Friday, July 2, 2010 10:44:10 AM
M Haidar Hmhaidarhanif # Friday, July 2, 2010 11:09:55 AM
Originally posted by zibin:
[I said this at the previous comment] But at least, just for comparison. Or maybe just put a snippet over there.
Ben Tudballtudsta # Saturday, July 3, 2010 4:44:24 AM
z@h3kZAHEK # Saturday, July 3, 2010 12:14:26 PM
Mehrdad Archenemyfmemof # Sunday, July 4, 2010 2:02:00 PM
Christopher Cooksonvirtualkiwi # Monday, July 5, 2010 11:01:13 AM
My Opera 10.54 auto updated to 10.60 and on restarting I received this message.
"Opera crashed while trying to show the crash dialogue for a previous crash."
I Tried a Windows System Restore, to immediately before the update, but that left me with NO Opera installed at all.
I fixed the problem in the end by downloading 10.54 and installing it as an 'upgrade' over 10.60, but only after a couple of hours of wasted time on Firefox trying to find a solution. I just hope Opera doesn't try to auto update itself again, as I depend on it for work, and can't afford hours of lost productivity, and don't anyone tell me to do a clean install, as last time I did that I spend hours getting everything back to normal so I could work.
Anonymous # Monday, July 5, 2010 11:02:07 AM
Bruce Lawsonbrucelawson # Monday, July 5, 2010 4:45:32 PM
Cutting Spoonhellspork # Monday, July 5, 2010 7:59:18 PM
You did not indicate which Windows, SP level, or CPU and GPU.
You did not indicate whether you have any custom userjs or usercss, or any custom certificates.
It is difficult to help someone when they do not provide much-needed information.
Christopher Cooksonvirtualkiwi # Monday, July 5, 2010 10:01:07 PM
I didn't see an uninstall restore point, only an upgrade restore point, and going back immediately before that Opera was gone.
As far as customisations go, I use a custom theme, and not really a customisation, but an installation option, I have Opera installed to use European Portuguese.
I did track down and run Google Translate on some comments in a Russian forum about the error message I received - incidentally it seemed to have occurred with an earlier upgrade, and they claimed it was related to locales. I tried to look at the settings they suggested, and didn't make any difference.
Cutting Spoonhellspork # Monday, July 5, 2010 10:30:27 PM
I have found one crasher in recent Opera, which occurs when using Facebook chat with multiple Facebook windows open. There are a few on ChromeExperiments but those should not count.
I have personally noticed that recent versions of Opera are more often reported to crash on AMD CPUs...? May be that some unique architectural quirk in the Athlon is messing with JIT. Beyond that, I must confess great surprise that you had such trouble on XP. I will set up a VM later, and try to set up Opera in a portuguese environment.
drunkrockers # Tuesday, July 6, 2010 12:29:27 AM
i cant find a way to put it back
bertho # Tuesday, July 6, 2010 1:42:50 AM
floppyears # Tuesday, July 6, 2010 2:34:19 AM
Dmitry Simonchikmylh # Tuesday, July 6, 2010 9:05:30 AM
Witold Barylukmovax # Tuesday, July 6, 2010 6:48:29 PM
At least 9 threads here! + pluginwrappers.
Maybe you mean that single tab/web page is serviced by no more than single thread? And as such, Web Workers will not use multiple cores on single web page?
Anonymous # Wednesday, July 7, 2010 3:04:17 AM
mryanmarkryan # Wednesday, July 7, 2010 1:52:18 PM
Cutting Spoonhellspork # Wednesday, July 7, 2010 6:19:00 PM
Originally posted by movax:
The whole of the Opera browser does not use multiple cores. Threads are inline, not parallel, and most of them spend their time idle.
Anonymous # Wednesday, July 7, 2010 6:59:41 PM