Further progress on Opera Dragonfly 1.1

,

We have made some refinements to the first preview of Opera Dragonfly 1.1, which we released on the experimental branch today. These include polishing the new search feature, and further updates to the Error Log.

Search

We have polished the look of the previous and next icons, improved the search highlight colours, and changed the search behaviour to optimise space and performance. We’ve moved the search match and number of hits to a badge inside the search field, instead of a status bar at the bottom of the view, and we have limited the number of search matches that are shown. Due to performance reasons, if you do a search for a short search term with thousands of matches it can freeze or slow down the UI when using the JavaScript search. To avoid this, we've limited the number of results that can be shown to 1,000. This will guard against locking up the browser, and you will mostly only run into this issue when you search for a too vague search term, such as a one letter search term. You can increase the number of matches shown in the settings, under the Scripts tab.

Error Log

We've updated the Error log to optimise the layout and display of error messages. Each error message should now be more compact. For the "All" tab, we have replaced the severity icon with the type of error, such as JavaScript, CSS, or Storage. We will use the severity icon in the filtered views for the individual error types, although that is not implemented yet. We also now show the context of where the error occurs, such as in a CSS style sheet, HTML style attribute, or the JavaScript event thread, etc.

Coming soon

Support for opening the CSS file at the correct line number from the Style Inspector style rule will come very soon. We will hopefully have another build this week with this enabled.

First preview of Opera Dragonfly 1.1More steps along the road to Opera Dragonfly 1.1

Comments

ouzowtfouzoWTF Tuesday, June 21, 2011 10:12:04 PM

up

d4rkn1ght Tuesday, June 21, 2011 10:17:06 PM

up

Martin KadlecBS-Harou Tuesday, June 21, 2011 10:21:52 PM

Hi, thank you for the updates smile

I found two related bugs.
1 - Adding/removing panels in error log doesn't work correctly
2 - Selected options are not remembered for the first time they are changed

I've also made a video with these bugs.
http://www.youtube.com/watch?v=aKEZzyL-Um0

IllusionMH109th Tuesday, June 21, 2011 10:43:09 PM

BS-Harou, this bug is in that click on labes(not directly to checkboxes) doesn't call onchange (or other) event.
It appears not only in error options.

Sorry, hadn't no time to fix this, because of exams in university.

Many nice changes in DF on this week. Can't waite to resume work.

JanGen Wednesday, June 22, 2011 11:47:46 AM

Great.

Will the CSS improvements also improve the behaviour to use an (already) open resource tab instead of opening myriad tabs with the same CSS file?

I can imagine that opening in another tab can be useful: shift click

JanGen Wednesday, June 22, 2011 12:01:46 PM

Greatest improvement in this build/Presto 2.9 seems to be that you can see all resources without the need for reloading.

So the track content setting is getting obsolete, if I'am not mistaken.

Evandro OliveiraEvandroOliveira Wednesday, June 22, 2011 12:13:22 PM

Hey! Awesome job!!! You're great, but... still waiting for a JS profiler :/
Keep up the good work!

Jimtoyotabedzrock Friday, June 24, 2011 3:12:00 PM

Shouldn't the search use web workers? To avoid any delay with the interface?

Christian Krebsaleto Friday, June 24, 2011 8:45:06 PM

Originally posted by toyotabedzrock:

Shouldn't the search use web workers? To avoid any delay with the interface?


Wouldn't help much. The issue is not the actual search in e.g. all the source files but to display them. You can very that by setting the "Maximum number of displayed search hits" in the script options to 101 (the lowest value) and search for e.g. 'e' in a document with a lot of scripts.

Write a comment

New comments have been disabled for this post.