Opera Next update – 21.0.1432.39

Hello,

We’re updating Opera Next to 21.0.1432.39. Inside you can find few bugfixes.

Opera will now scale with screens that use 200% DPI setting in Windows. You can check full list of fixes in the changelog.

Be sure to try it out and share your thoughts with us.

Highlights

  • Opera will scale with 200% DPI screens

Downloads

Full changelog

Opera Developer 22.0.1460.0, now easier to update than ever

There comes the first Opera 22 update that will benefit from the new silent update process on windows. You should be upgraded to it automatically, without even a UAC prompt.

In addition, to make the autoupdating even smoother, the autoupdate packages will now be sent to you in the form of a patch instead of a full package, whenever possible. This will hopefully help those of you who pay per Mb downloaded or those who have a strict monthly download quota,

In addition to this, this build also contain a few bug fixes and crash fixes. See the changelog for the full list.

For those of you who are curious or need more information in order to produce a better bug report, here are some more technical details:

The silent autoupdate feature is implemented using a scheduled task. Those of you familiar with the Windows Task Scheduler should be able to use it to retrieve information about the task. The scheduled task is supposed to run on system startup and every day initially, but we can adjust it run every few days instead if we need to reduce the load on our servers. When Opera is running, it will keep track of whether the scheduled task is running normally and will attempt to run it manually when needed. If all else fails (which should really not happen), Opera will fall back to running autoupdate itself and in such a case, UAC prompts might appear anyway.

One important exception to silent autoupdate happens if you have installed Opera from a standard user account and elected to install for the “Current User” to a folder requiring administrative privileges. The installer will allow you to proceed as usual, but it will not create a scheduled task. For installations made in this fashion, autoupdate will keep working as it used to instead and UAC prompts might appear. This is obviously because creating a scheduled task allowing silent installation from the standard user account would be impossible.

The patch packages also have their own interesting story. They are generated using bsdiff between a pair of full package. Since we release quite a large number of packages, we can’t realistically create patch packages for every single pair of packages we release (the time required and the amount of storage needed would be prohibitive). Therefore, we only generate patch packages from those pairs which we consider likely to be used as an upgrade path. In other words, if we think many user will upgrade from version X to version Y, there will be a patch package for it. And if we think it is unlikely that people will upgrade from version X to version Z, people using version X will be served a full version Z package when autoupdating.

The process of applying the binary diffs from the patch package is quite simple: First, your opera installation will be copied entirely to a temporary folder, then bspatch will be used to apply the diffs. If applying the diffs fails (and this should really not happen), then a full package will be downloaded and used instead. Finally, when the patch has been applied, the installer is run from the patched opera folder, as if it had been run from a full package, and upgrades the actual opera installation.

That’s all the technical infos for today. Stay tuned for future info about opera in general and autoupdate/the windows installer in particular. As usual, any feedback or bug report is greatly appreciated.

Known issues

  • opera:extensions and opera:plugins are blank
  • opera://about/thanks is shown as plain text
  • [OS X] Crashes when clicking Reload in toolbars asking users to reload to recover from a crash

Downloads

Opera Developer 22!

Today marks the first release of Opera Developer 22. For this initial developer release our primary focus has been on backend changes to ready ourselves for future improvements in the UI and elsewhere.

Nonetheless, 22 is a major update and includes hundreds of bug fixes, crash fixes and site rendering improvements (see our changelog for the full list).

In addition some UI improvements are already visible, such as a new Encoding Menu, an update to our default themes and a better (silent) update process on Windows. Our new silent update allows for a more seamless update to the latest version. There are no buttons to click and no UAC (User Account Control) dialog interrupting your workflow. You will be automatically updated to ensure you always have the most recent and most secure Opera version.

Note: This build will not silently update, that will happen from the next Developer release.

Thanks again for your testing and feedback, which is (as always) greatly appreciated!

Highlights

  • Update to Chromium 35.0.1883.0
  • Silent update
  • New default themes
  • Encoding menu

Downloads

Full changelog

Opera 21 Next includes an option to show the full address

Opera 21 moves from the Developer stream to the Next stream.

Most of the changes are under the hood. Opera 21 supports Aura, a hardware-accelerated rendering of the browser. This enables less-taxing user-interface animations and a sleeker, more responsive feel to the whole UI. It also gives us a solid foundation on which to make future UI changes.

Aura is a big change, but we’ve also included a small change that will please many of you. There’s now a setting to make Opera always show the absolute address, the full URL, in the address field.

While many of you appreciate our emphasis on the domain name and our decision to display only the essential information, our power users and web developers often need to see the full URL. Now, they can. Simply enable the advanced settings and select show full URL in combined search and address bar under Opera’s user interface options. It’s “Hello, absolute address!” from then on.

As usual, we’re hugely grateful for your bug reports and comments. Thank you.

Downloads

Full changelog

Opera Developer 21.0.1432.24

Are you ready for testing the first Opera Developer release of Spring 2014?

We have a couple of crashes and bugs fixed for you today. The release also includes Chromium update version 34.0.1847.76.

You can check full list of fixes in the changelog.

Give it a try and give us a poke by commenting or reporting bugs  :)

Highlights

  • Chromium Update 34.0.1847.76
  • Dragging speed dial items onto bookmark bar moves one of them to a speed dial folder
  • Sliding toolbars disappear when switching tabs

Known issues

  • [Mac] Bookmarks bar titles truncated

Downloads

Full changelog

Opera 20.0.1387.77 update

It’s been a while since I posted here, heh?

Spring is coming at an impressive pace in Europe: last year we still had snow in April, but this year we probably would be able to start the swimming season in less than three weeks.

But enough of swimming plans. Here’s something more important we’re keeping pace with – our release cycle. Today we’re updating Opera Stable stream.

This updated version includes stability fixes and a Chromium update to 33.0.1750.149.
You can read more about the update on our Security blog

Happy surfing!

Download Opera

Full changelog

Opera Developer 21.0.1432.5 – fun with tabs!

Since I work on the Engine part in Desktop, this blog post will be slightly more “engine-ish” :) .

At first, I would like to present to you our latest Opera Developer build – 21.0.1432.5, which contains a few important fixes – Adblock is fully working again, tabs on Mac won’t do the Harlem Shake on hover anymore, and a couple of crashes are fixed. You can check full list of fixes in the changelog.
Today, we’re also giving you a sneak peek of our latest features connected with improving start-up time – especially helpful when restoring session with many tabs. There are few different approaches – they are all available as separate feature-flags at opera://flags:

  • #delay-onload – This one is my favorite :) – after restoring session, onload JS events in background tabs aren’t fired until a tab is activated. It might not sound that important, but during tests this feature was giving the best results – both in loading times, and CPU/memory usage.
  • #extended-lazy-session-loading (requires #lazy-session-loading being on) – causes that an active tab + the configured number of tabs (still working on the number, for now it’s 2) is being loaded normally when restoring the session. When any of tabs finishes loading, it triggers the next one to start loading, until all tabs are done. It takes more time to fully restore session, but the start-up itself is much quicker it and takes less CPU.
  • #restore-contenteditables-state – the content of elements with contenteditable=”true” is restored on session restoration/history navigation.
  • #tab-hibernation – If a background tab is inactive (does not load anything including XHRs, plays any media, plug-in is not streaming any data, or a script is not changing page’s title/favicon) for 40 seconds its process gets suspended and swapped out (causing process memory usage drops significantly). Swapping out happens instantly on Windows and is driven by OS on mac. If the process is shared between couple of tabs, all of them have to be inactive for this to kick in.
  • #session-tabs-serialization – all pages from opened tabs are serialized on HDD when closing the browser and are loaded from there instead of the network when restoring the session. This feature should be especially useful for the users with low bandwidth network.

They are all still under heavy development, but, of course, you are very welcome to test on your own each one of them right now. We’re very curious about your impressions and feedback – also, if you found any issue with specific page, please report URLs and feature name.

PS. remember you have to restart browser to make flag active – so, for example #session-tabs-serialization, which makes a lot of work during browser shut down, will be applied after second restart.

Highlights

  • AdBlock is working again when opening pages in new tabs

Known issues:

  • No thumbnail is created for new speed dials

Downloads

Full changelog

Opera Developer 21.0.1432.0

We’re rolling out a new Opera developer update. This includes bug fixes. Bookmarks which are dragged from Bookmarks Bar to Tab Bar are now opening in the proper place on Mac – not as the last tab. The behavior of download notification button is also fixed – it was still visible after cleaning the download history and now it’s hidden like it’s supposed to.

You can check full list of fixes in the changelog.

Let us know if you’re having problems with our current Developer stream. And if you’re curious, I’m Wojtek. I’ve recently joined the team as a Mac Product Tester. Looking forward to getting your feedback about this update! :)

Highlights

  • The Off Road section of the help page is displayed after turning on Off Road Mode for the first time
  • Bookmarks dragged from Bookmarks Bar to Tab Bar are opening in the proper place

Known issues:

  • Some Speed Dial thumbnails are not generated when a new page is saved to Speed Dial
  • Downloads pop-out can refuse to Open on Mac

Downloads

Full changelog