Latest stable release with recent enhancements

March 16, 2012 · by Patrick H. Lauke

Today's release on the stable branch of Opera Dragonfly includes many of the recent enhancements and fixes from our experimental builds.

Apart from a boatload of small tweaks and bug fixes, some of the top new features and additions include:

CSS shorthands in the Style Inspector, which removes a lot of the redundancy of having all expanded and default styles being listed
JavaScript runtime errors shown directly as a tooltip in the Script panel, rather than just in the Error panel
More dynamic JavaScript value inspection with a powerful tooltip that now also allows for function evaluation
Improved script selection dropdown, with filtering and improved keyboard support
The style panel now also allows you to use your preferred color format (Hex, RGB or HSL), which can be changed in Settings → Documents → Styles

These features have been in our experimental builds for a while now, so we're very pleased to now unleash them on our stable release branch. As ever, we welcome our users' feedback and suggestions. Enjoy!

Readers' comments 15

Left under the original article, as archived.

Martin KadlecFriday, March 16, 2012 5:19:29 PM
good job

btw, can we expect some update for Profiler anytime soon?
NimeshFriday, March 16, 2012 5:51:13 PM
ПавелFriday, March 16, 2012 6:20:16 PM
Thanks, js, css and dom inspectors have completely replaced firebug!) There is only a network inspector)
d4rkn1ghtFriday, March 16, 2012 6:39:07 PM
Unregistered userFriday, March 16, 2012 7:21:24 PM
Anonymous writes: Great changes. Only thing I'm missing from Dragonfly now is Firebug-loke console where I can track ajax requests.
D1sasterp1eceFriday, March 16, 2012 8:15:22 PM
Dropdown menus (UI Language, Monospace Font settings etc) in settings don't work for me and this is for all three branches of Dragonfly. What may be the cause?
Eli MitchellFriday, March 16, 2012 11:42:03 PM
Fantastic. I'm glad I can evaluate functions now.

Could you add a feature where we could have the ability to exclude browser.js from being searched when I select "all files" in the search tab in the scripts panel? Yesterday I was searching all scripts on a page for "opera" and I had to wade through all of the appearances of that phrase in browser.js.
Christian KrebsSaturday, March 17, 2012 11:36:03 AM
Originally posted by cyberstream:

Could you add a feature where we could have the ability to exclude browser.js from being searched when I select "all files" in the search tab in the scripts panel?

If you uncheck "injected" then it will not search in Browser JS (also not in any user or extension JS). Do you need a separate checkbox for Browser JS only?
Eli MitchellSaturday, March 17, 2012 9:08:17 PM
Actually, I guess that would work fine. I didn't think to try that. Thanks.
Unregistered userWednesday, March 21, 2012 4:16:03 PM
ozoratsubasa writes: It's more beautiful :)
Martin KadlecFriday, March 23, 2012 12:42:43 PM
Web inspector has implemented very cool feature - breaking NodeLists and Arrays down into ranges. This could be especially useful for large canvas byte arrays that currently can freeze Opera for a long time.

http://d3j5vwomefv46c.cloudfront.net/photos/full/544436409.png?key=231265&Expires=1332507364&Key-Pair-Id=APKAIYVGSUJFNRFZBBTA&Signature=FH2ICz4gmEe2AjHFdXTQxOELymlTvDfyprkK9dAbmqAH5T81iQdNxFmt3~ITlf-FGTmjghDlPpoPBGmPjVWyteT4EXKQh6TX3RcLoUHEwkIrA1DcFijmsSY3SWbmlv93xgtvWd-ooPmn0fES4JWR-8xkGAOuBDdTy5uODFhttuA_ -
Constantine VesnaFriday, March 23, 2012 5:48:04 PM
Congrats with stable release!

// eagerly waiting for script beautification, live script edit and profiler
JanghouTuesday, April 10, 2012 12:49:59 PM
I saved some interesting pages as mht, for checking out later.

But Dragonfly can't do anything with them (yet?).
Well it showed a small DOM with:
```
< object id="omf_body_part_1" 
        type="text/html" 
         data="attachment:/335/default.htm">
   Mail body
</object>
```
which did surprise me (Mail body),

but I couldn't locate or check any DOM or CSS.
JanghouTuesday, April 10, 2012 1:31:13 PM
Another helpful CSS debugging tool would be i we could disable a CSS property globally for a page.
Like disable all gradients or disable CSS transform or CSS animations
Off course we can add an important rule but
For disabling gradients:
* {-o-background-image: none !important}
also removes all images.
JanghouTuesday, April 10, 2012 2:23:18 PM
I tried to debug a site with all CSS (8k) on one line. Not nice
A simple replace "}" with "}\n" would help enormously to make the CSS more understandable in the resource tab.

And how do we handle media queries.
does DF give any info about them at the moment?
Is there any way to dis/enable them,
Is support planned?