coderus | # 171 | 2013-06-10, 09:28 | Report

QmlMozBrowser v0.1.6.4
+ Added searching text on page
* Fixed saving user agent
* Minor fixies

http://coderus.thecust.net/harmattan....6.4_armel.deb

Vromoth | # 172 | 2013-06-11, 08:58 | Report

What causes the browser to open more slowly than the standard Web browser? That would be my biggest problem.

Edit: Also whatever user agent I use I almost always get the desktop site rather than the mobile one. (google, bing, twitter, Facebook ... ext.)

---

Last edited by Vromoth; 2013-06-11 at 09:36.

setter | # 173 | 2013-06-11, 09:52 | Report

Same problem here, every big newspaper here in Sweden will load the desktop version instead of the mobile one.

juiceme | # 174 | 2013-06-11, 11:56 | Report

Well that could have something to do with the fact that grob is always running on the background and only draws up the UI wen you invoke it

don.edri | # 175 | 2013-06-11, 12:08 | Report

This browser is getting more awesome with every update Are developers planning on supporting tabbed browsing?

Vromoth | # 176 | 2013-06-11, 12:55 | Report

Ok, thanks. And there is no way to do the same with qmlfirefox and disable grob? I'm just assuming here that grob is the default browser rather than a wider system proses which it probably is.

setter | # 177 | 2013-06-11, 13:59 | Report

If I go to https://touch.facebook.com the icon on the top left corner doesn't work. A click on that icon should bring up favourites, pages, groups, etc. Is it only at my phone it fails?
Works nice with grob.

Eztran | # 178 | 2013-06-12, 00:35 | Report

It seems to be using a generic FF24/Linux UA string rather than the one given, whether the option is ticked or not.

wolke | # 179 | 2013-06-15, 23:01 | Report

url loading bar blocks access to the top of the screen, making it impossible to interact with, say, facebook notifications until the full page has loaded.
the url bar is dismissable when the page is finished loading, but not before. {note that the url bar stays loading for 2min on facebook}

some ideas:
1) dont differentiate between the loading state and the non-loading state. it the users wishes to wait for the page to load properly before interacting, they can, if not they just tap empty space like normal.
2) indicate loading at the bottom, where the user can scroll/zoom to get at the things underneath
3) move the url bar to the bottom, where it is less likely to interfere
4) make the loading url bar look very different than the url bar, make it a little more transparent, and let the user tap stuff underneath it. {allow interacting with it only after you bring up the overlay.}

Greendts | # 180 | 2013-06-16, 10:18 | Report

Any chance of implementing a cleaning function within the app?? Otherwise everything else seems flawless