View Single Post
marxian's Avatar
Posts: 2,448 | Thanked: 9,523 times | Joined on Aug 2010 @ Wigan, UK
#95
Originally Posted by Estel View Post
After some extensive usage, I've found one "major" bug with QML Browser, and got idea for two small, yet nifty enhancements:

Bug:

1. Once, I required to turn network access off, while QML Browser was loading some page (at the same time). Immediately, QML Browser literally spammed me with "select network" maemo popups. Upon dismissing it, new one immediately popped up, all the time. What's even worse, actually selecting network and connecting haven't helped - it seems that large number of network connection requests got queued every second, and system was just executing all of them, one after another.

Add to this fact that network connection pop-up is impossible to minimize, and you get the picture. Summing it up, I had to kill QML Browser via ssh, from another device.
There is no bearer management code in QML Browser. Everything is handled by QtNetwork and QtWebKit. I will take a look at where the re-connection requests originate from and decide where it is best to implement handling of such cases (components or application).

Originally Posted by Estel View Post
Suggestions:

1. It would be nice, if browsing history via from-right swipe would be accessible even on the bookmarks screen (the one that appears after starting QML Browser). It's quite silly, that we need to open any_random page, before being able to select what we really want, from browsing history.
You can select from the full browsing history by tapping on the combobox arrow in the text field. The 'recent history' is unique the specific WebView instance (so if you have two browser windows open, each 'recent history' is different, just like in MicroB), and is only availble when a page has been visited in that WebView.

Originally Posted by Estel View Post
2. Not sure if it's doable here, but all major desktop browser seems to remember last used zoom level for given site (unless private data gets cleared... I hope).

It would be nice, if QML Browser could do that, too. there are many sites optimized for 1024 resolution as minimum, which require exactly one zoom-out in QML browser, to be fully usable. Repeating it for every visited page gets tedious - even more for sites, that actually require more zoom-outs. Having them render initially at last used zoom level would be great.
I don't think there is anything in the QtWebKit settings APIs that would allow me to do this. It is of course technically possible to do it, simply by storing the values in an appropriate format, but I'm not sure what that format would be. It would depend on what else was to be stored besides the zoom level.

Originally Posted by Estel View Post
Additional suggestions:

1. I think that adding one-liner required to make QML Browser act as default system browser to the first post would help many people (just like Open Media Player does it).
Well, I was not ready to suggest that people make it their default browser. The project's main aim has always been to help me test the components in a real-world scenario.

Originally Posted by Estel View Post
2. The "lacking features" point about scrolling with cursor keys is actually misleading - up&down arrows scrolling works fine, at least here. Haven't checked left&right scrolling.
The cursor key handling was only implemented in the last update, following implementation of custom key event handling in the components. I've now removed that reference from the first post.
__________________
'Men of high position are allowed, by a special act of grace, to accomodate their reasoning to the answer they need. Logic is only required in those of lesser rank.' - J K Galbraith

My website

GitHub
 

The Following 2 Users Say Thank You to marxian For This Useful Post: