Hello Opera 10.60

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

Peacekeeper benchmark comparison, showing Opera 10.60 in the lead: Opera 10.60 - 6844; Opera 10.50 - 4056; Opera 10.10 - 1924; Chrome 5.0.375.86 - 6173; Safari 5.0 - 4021; Firefox 3.6.6 - 2890. Tests carrried out on Windows Vista / Intel Core 2 Quad Q8200 2.33GHz 3GB

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.

Opera 10.60's Geolocation bar

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.

WebExpo Tour - Geeks on the roadScreencast: "Mobile web development techniques"

Comments

Witold Barylukmovax Wednesday, July 7, 2010 11:59:18 PM

Originally posted by hellspork:

The whole of the Opera browser does not use multiple cores. Threads are inline, not parallel, and most of them spend their time idle.



So, there is explicit scheduling and explicit BIG LOCK in every thread, where it is safe to be preempted? This is really strange. It is very rearly used. So you are actually not using Threads, but construct called "Fiber"!

Can you explain if i'm correct, and why you choosen such architecture (despite no need to do any synchronization in the Opera).

Chaos fon Kernel7r35p4553r Thursday, July 8, 2010 8:32:30 AM

Chaos fon Kernel7r35p4553r Thursday, July 8, 2010 8:36:07 AM

And make lower mem&cpu consumption.

pcdemon82 Thursday, July 8, 2010 11:50:01 AM

This version don't work on Windows 9x. sad

I choose mainly Opera because until 10.50, was the only modern browser still compatible with 9x systems. Actually I use 10.10 ONLY for using advanced javascript (watching videos, posting in some forums, ecc...) and for Opera Unite. For the rest I still use the fastest, less graphical, good old fashioned 6.02 >>Beta<< version (I want to highlight this wwww).

Note: W = lol in Japan

Exolon Friday, July 9, 2010 1:32:30 AM

This is the first version since 10.10 that seems stable on my Mac running OS X (Leopard). Had to roll back after all of the 10.5x releases due to frequent, apparently random crashes (even when the machine was idle for some time).

After a strange issue immediately after installing 10.60 - Opera would hang in a busy loop until killed - I rebooted and since then, a few hours ago, Opera has been running smoothly. Hopefully it's really fixed, well done guys!

Unregistered user Friday, July 9, 2010 2:57:00 AM

Benzyl writes: 10.10 worked fine under OSX 10.5, 10.53 didn't even start up all the way and while 10.54 worked (after a fashion) it was the slowest and most processor intensive thing I've ever seen stumbling broken leggedly towards the middle distance. I dread to think what 10.60 will be like as I now have rigidly fixed low expectations of the near future of the main browser I've been using since about 7 on both PC and mac.

AndyAndySolo Friday, July 9, 2010 1:51:46 PM

Hey fellas. Does anyone has this wierd fonts issue? As I am typing its crazy "halo" all-caps fontface. What'ta'hell?

Cutting Spoonhellspork Friday, July 9, 2010 5:47:06 PM

pcDemon82: Using 10.54, 10.10, 9.64 on my Win9x smile

Exolon, Benzyl: DesktopTeam has already pushed a test version with another big MacOS stability fix. Go take a look.

Andy: What Operating System? If you are not using Windows or Mac, please list your distro.

CEHorn Friday, July 9, 2010 8:47:45 PM

Moderator edit: This comment has been removed for breaching our terms of use.

Cutting Spoonhellspork Friday, July 9, 2010 11:03:15 PM

my.opera.com/desktopteam/blog

They've pushed some candidate builds for an additional Mac stability fix. They're seeing all of these crash logs, and maybe now a few more crashers will disappear within the week.

Gordongorodn Saturday, July 10, 2010 7:40:02 AM

I've just spent 5 hours scraping 10.60 off my computer and reinstalling 9.51. I did the upgrade path, straight over 9.51.

1. Wikipedia changed from Verdana 10pt to Times New Roman 9pt.
2. Clusty/Yippy disappeared from my custom search, but Bing appeared in its place.
3. All form text entry fields used Times New Roman 9pt rather than Verdana.

Yes, I did immediately change the Preferences>>Fonts to my prefs -- it didn't do anything over two days.

This is the only app I have ever seen that changes prefs on upgrade. I'm not giving up on Opera, but right now I would love to see a retail version that gives users some leverage. IE never changed my prefs on upgrade!

Gordon.

Exolon Sunday, July 11, 2010 1:09:17 PM

After a couple of days, I'm still pretty impressed. The main differences, performance-wise for me, are:

1: Very slightly higher CPU usage than 10.10 and 10.5x (about 9-10% on average ATM, with lots of tabs open but no Flash objects running)
2: Slightly lower resident memory usage - about 680 MB at the moment, albeit soon after a crash/restart of Opera. 10.10 was taking up about 1 gig of RAM.
3: Crashed twice in about 2 days - not ideal but a huge improvement on the 10.5x releases.

Cutting Spoon: Thanks, glad to hear the Mac crashers are being worked on. I used to constantly run beta builds for a while (with the 9.x releases), but on my Mac migrating preferences/sessions between release/beta is a bit of a pain so I won't this time. The crashes have at least been a lot fewer than in the 10.5x builds (which were horrendous, crashing at least once per hour on average), so I can stick it out until the next proper release.

Things are getting better IMO. smile

abhrapro Sunday, July 11, 2010 3:00:40 PM

gr8 news.just wish it could support proper indic language rendering

Zhu Daomingdaoming Tuesday, July 13, 2010 9:28:30 AM

i love the opera browser since birth. the only thing i wish the developers will add to its development is faster support for flash. loading crawls mostly on flash based applications. but the rest loads smoothly. aside from sync, unite and turbo, another cool feature that i could think would be nice is the ability to integrate it to popular social media networks, perhaps via panel or a toolbar.

Cutting Spoonhellspork Tuesday, July 13, 2010 6:20:10 PM

I think you're talking about something like Flock. Some people like it, I mostly don't. You can place bookmarked pages into your Panel/sidebar, if your screen is big enough this may work well.

Charles SchlossChas4 Wednesday, July 14, 2010 6:38:58 PM

Safari 5 seems to do http://people.opera.com/danield/webapps/web-workers/ with out web workers faster than with web workers confused

edi temposetempos Thursday, July 15, 2010 3:11:47 PM

Trying to build an idea, through writing a blog on Opera, hoping the body and grow with Opera.
Greeting
Edi tempos
my.opera.com/etempos

Cutting Spoonhellspork Friday, July 16, 2010 12:01:05 AM

I think in many cases, the worker will not be faster unless it runs completely separate. However even right now, there are things that workers are much better suited to do.

Also Opera works with most multiwindow and inter-window Chrome Experiments, would be nice if GMail reflected this with persistent child windows in Opera 10.60.

Exolon Friday, July 16, 2010 1:00:15 AM

Originally posted by Chas4:

Safari 5 seems to do http://people.opera.com/danield/webapps/web-workers/ with out web workers faster than with web workers :confused:


It seems that this release is still single-threaded, so the threading model for web workers is presumably similar to "green threads" in some programming language implementations (e.g. Ruby 1.8).

If the web workers in the test page are all doing compute-intensive tasks, then handling them all in one physical thread will not save any time. In fact it will probably slow things down since there is some overhead involved in context switching between workers.

OTOH, if some of the workers are carrying out blocking operations (i.e. waiting for I/O) then there will be a benefit.

Apparently a multi-threaded Opera is on the way, though, which will take advantage of multiple cores.

Exolon Saturday, July 17, 2010 12:24:59 AM

Just tried out the new WebM/VP8 codec in Youtube and was shocked by how CPU-intensive it is - both Opera and the nightly Firefox build are taking ~110% CPU (i.e. hogging more than one core) on my Macbook, where the Flash player was taking ~50% CPU and the H.264 codec in Safari is using ~20% CPU time.

Looks like VP8 is currently unaccelerated (at least on OS X, due to Apple not standardising some API for GPU use) but still, ouch.

Metal Warriormetalbrother Saturday, July 17, 2010 5:30:05 AM

Bad !
opera 10.60 does not support video in html
I have my personal page and I added the audio and video in html the opera 10.54 support it but 10.60 NOT
Now with 10.60 I cant use the video html

berend ytsmaytsmabeer Saturday, July 17, 2010 7:16:27 AM

Originally posted by metalbrother:

Bad !
opera 10.60 does not support video in html
I have my personal page and I added the audio and video in html the opera 10.54 support it but 10.60 NOT
Now with 10.60 I cant use the video html


What sort of video you where using.
video is supported trough < video > tags

Cutting Spoonhellspork Saturday, July 17, 2010 9:22:52 PM

It should work great unless you had an upgrade problem.

Jason RaeJayraeca Friday, July 23, 2010 3:17:59 PM

I must say that I prefer the last version of Opera. My Samsung phone won't even run it, and t9 doesn't work at all. Not at all impressed. More of a pain in the ass than anything.

Charles SchlossChas4 Friday, July 23, 2010 3:35:19 PM

Originally posted by Jayraeca:

I must say that I prefer the last version of Opera. My Samsung phone won't even run it, and t9 doesn't work at all. Not at all impressed. More of a pain in the ass than anything.


This is about the desktop version, you are talking about the Mobile version, try in the forms

Jason RaeJayraeca Friday, July 23, 2010 4:19:01 PM

My error.

Jishnu Devanjishnudevan Sunday, July 25, 2010 3:11:14 AM

when i click on webm and ovg theora videos it opens a download pop up and does not play

Jishnu Devanjishnudevan Sunday, July 25, 2010 3:12:00 AM

scribd is not shown properly in opera

Unregistered user Tuesday, August 3, 2010 9:49:29 PM

bitoclass writes: I'm running Windows 7 64-bit on an Intel CPU and I am getting the same problem as Christopher Cookson described here: http://my.opera.com/ODIN/blog/hello-opera-10-60#comment33546832 An extra frustrating part is that the error says "A crash log was created here: C:\Users\[me]\AppData\Local\Temp\crash[longnumber].txt Please send us this log manually." but doesn't indicate where to send this or what will happen if I do. Will someone assist me with getting Opera, my primary browser, working again? This is really frustrating as I simply can't run Opera now :( Can anyone assist?

Cutting Spoonhellspork Wednesday, August 4, 2010 4:55:29 PM

bugs.opera.com/wizard

Create an incident using the short form, then send the file in the next step.

You may also wish to download the second-newest 10.70 snapshot (classic installer) and quickly check how it works. Remember to install in a different folder (Desktop/10.70) and tell it to store all settings in the program folder. If it doesn't work, uninstall immediately and include the info in the bug report. Public testing releases are on my.opera.com/desktopteam

prd3 Tuesday, August 31, 2010 8:52:01 AM

Originally posted by troll:

Oh the happy days when Opera could fit on a floppy or two.


Yeah, back when it didn't support even a tiny fraction of the web standards that are supported today. Do you think supporting all the new web standards is possible while still fitting on a floppy? LOL.

Write a comment

New comments have been disabled for this post.