New Kestrel snapshot fixes Opera Dragonfly issues
The weekly snapshot of Opera Kestrel included a few fixes to bugs that caused issues in Opera Dragonfly. The most prominent one of these is that persistent cache should now work in Opera Dragonfly, enabling offline mode to work as it was designed. This should make Opera Dragonfly much more useful.
In further news, we are doing our best to try to squeeze the single windowed docked mode into Opera Dragonfly alpha 2. This hopefully wont delay what we've already planned for the second alpha. It wont be the final solution, as we need to do some interaction design work on how it will work differently to the separate window solution. As there is less space to work with, it will likely be more optimal to have a different view. The initial work will likely just make it work in that view, and test out the functionality given to use from the Desktop team.
In a post alpha 2 release, we hope to redesign and optimise the UI somewhat, and work on keyboard accessibility. The ground work for the later has already began. I've been reading up on WAI-ARIA, and it looks like something we can put to good use. As well as making controls accessible to assistive technology, it should make our keyboard navigation work more like a native application for those controls. There are a number of roles for components that stand out instantly as useful for Opera Dragonfly, including
treeitem for the DOM source code tree,
search and perhaps
checkbox for the toolbars,
tabpanel for the tabs,
breadcrumbs for the DOM path and so on. It looks like ARIA should be something that isn't too difficult to learn or apply.
One of the great things about developing Opera Dragonfly in Web technologies (except being a useful exercise in finding Opera bugs), is that we can design only for the Web standards provided by the Core-2.1/Opera 9.5 platform. Opera has one of the most advanced support for Web standards in the industry, and we don't have to care if they are supported yet in another browser. I'm specifically talking about Web standards here, not vendor only solutions, that will cause lock-in. We can use Opera Dragonfly as a showcase of what is possible with the likes of accessibility on the Web. My next mission is to try to get the team to use SVG images in the interface. With SVG we can make the backgrounds of buttons as a reusable element (styleable through CSS SVG profile), use a CSS sprite to reduce the HTTP traffic, and zip as SVGZ to reduce the file size even further than what SVG would already give you. SVG will also allow the button styles to be programmatically changed. An example could be detecting the platform and changing the button shapes or colours accordingly. This is not something we've planned yet, but is certainly something that is possible when we don't have to care about IE.