What’s New in Opera Dragonfly with Opera Next

New Release Model

You might have seen the flurry of updates in Opera Dragonfly – we now have CSS shorthands and also a style profiler! To make all this possible, we have also altered our release model.

Previously, we used to support older versions of Opera even with new releases, but it typically resulted in broken performance. Since Friday, we freeze a given Dragonfly version to an Opera version. This means, if you use a newer version of Opera, you get the latest, fastest version of Dragonfly that is stable and is confirmed to work on that version of Opera.

If you use remote debugging, be aware that this change may require your browser to load a previous version of Opera Dragonfly if connecting to an older browser version.

Local Zip Files

We have also vastly improved our build tools. You can now use a local version of Opera Dragonfly. What you might not know is you could also use them direct from the zipped file – less work for you! After downloading the zip file, you should set the Developer Tools URL in opera:config to:

file://localhost/<path to>/client-en.zip/client-en.xml

If you are a user of another locale, just download the appropriate locale zip, e.g.

file://localhost/<path to>/client-es.zip/client-es.xml

Zipped files are available for: latest build, cutting-edge, experimental.

JS Runtime Errors

Previously run-time errors were dropped in the console, but now you can actually see the line number and the script resource where an error occurred. Note that you currently need Opera Next to use this feature. Here is a screencast of this new feature in action:

Do note that, at the end, I show some features that are not yet part of this experimental build, but will be soon. :)

To use the experimental build of Opera Dragonfly, set the URL for opera:config#DeveloperTools to:


Please try it out and let us know what you think of it!