Notices

Using QMLBrowser with the virtual keyboard: after typing a URL and pressing enter, the main screen is shown again but the browser does not go to the URL. It requires opening the physical keyboard and pressing enter there.

Been using the qml-browser for a while, and I have to say I like it. I would like to ask would it be of any benefit to compile the qml-browser also with thumb2 ISA to gain smaller memory consumption. Although it seems that qml-browser already uses little less memory compared to microb (assuming microb is responsible for both brwoser and browserd processes). This is just an idea, not really an feature request, because I'm more than happy with the pace this software is progressing. Thank you very much.

Feature Request
1-Remember passwords for autolog in
2-pressing enter with virtual keyboard doesn't load the website(i have to press physical key)
3-changing default language to english because when i open google or wikipedia or other sites it loads the italian version of the webpage

Why only a quater of my avove post is appearing ???

Bug report (might be on the QtWebkit's side, if so - please forward it)

1. Set the iPhone 4S user agent (you can copy it from UserAgentTool)
2. visit http://m.demotywatory.pl
3. Do NOT set fullscreen
4. Scroll down
5. Scroll up (both via touchscreen)

Expected outcome - normal scrolling
Actual outcome - the top "DEMOTYWATORY" bar is painted multiple times, making part of the website content unreadable.
This doesn't happen on fullscreen.

Sounds similar to the issue I think I reported earlier whilst scrolling on slashdot, but that was without changing user agent

This sounds a lot like something I've been seeing in the Linguine app, which uses a raw QWebView widget to display html data. So I would suspect this is a feature of QtWebKit.

In fact, I've just gotten it to display that effect with that website. I'll append a screenshot. (Please ignore the "Reuters" tag on the menu bar. )

Whooooray, volume-key zooming! This mark the day when QML Browser become usable for everyday use, in my case.

It works great - but, as expected, I've encountered few bugs:

1. Sometimes during fullscreen, all interface buttons stop working (the one for switching out of fullscreen, swiping from left for cursor or from right for history - nothing works), while rendered page can still be scrolled and used normally. What's interesting - if I get out of fullscreen by sending:
... I can access the top-bar menu (new window, etc), but clicking those doesn't produce any results (they turn blue, indicated that they were clicked, but that's all about it). It looks like whole interface gets stuck.

I haven't found a way to reproduce it reliably, but it happens relatively often.

2. Cursor mode works somehow strange. If I use it directly after swiping (without clicking on cursor icon to make it sticky), I can't highlight text for copying by using shift - it just keep scrolling page.

Hoever, if I set it to sticky, all text that it hover over gets highlighted, even without holding shift.

3. As for the issue reported by marmistrz and explained by Copernicus, it is also perfectly reproducible without switching user agent, as long as page is still loading. If it stops loading (either by itself, or via cancelling), issue disappears.

/Estel

http://talk.maemo.org/showpost.php?p...2&postcount=72

I can also occasionally reproduce the non working fullscreen window.

I am also finding this issue posted by chill slightly annoying.
http://talk.maemo.org/showpost.php?p...1&postcount=81

It's starting to become my default browser.

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.

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.

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.

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).

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.
---

Thanks for your continued work on this!

/Estel