I think such features are designed to overcome the limitations of crapacitive screens, where the accuracy is much lower than on the resistive screen of the N900.

Anyhow, I will expose the hit test result API to QML, then give it a try. It will likely require several hit tests to acquire a selection of links to choose from.

Procedure is something like:

1. Get co-ordinates of screen tap.
2. Perform hit test on the co-ordinates, to see if there is a link.
3. Perform hit tests covering several points within some arbitrary radius of the tap.
4. Display links.

I can't claim any credit for the rendering speed. I'm just using the QWebView widget.

I haven't come across that, but QWebView does sometimes cause issues with painting, so it could be that the window and it's child widgets were not re-painted when attempting to exit from fullscreen.

For me, it behaves exactly like MicroB. It's activated by a swipe from the right edge of the screen, or long-press on the 'back' button. The logic for detecting the swipe is quite fuzzy. If anything, I would say it is too easy to activate.

Yes, but the QWebSettings::PluginsEnabled attribute is disabed by default, so I need to enable that first. I will provide more comprehensive settings in future updates (and also view-source etc). The APIs are there, I just need to implement them in the application code.

There's some documentation on the QtWebKit plugin support at http://qt-project.org/doc/qt-4.7/qtw...9-dc75fc65d6b6.