I think that another interesting thing to store, would be last used position in page, when using back/forward. Desktop browsers put you exactly where you have been, while QML Browser just bring you to the top of page (after back/forward). Well, just like sixwheeledbeast, I'm starting to use it as my main browser for N900 It's that good! Even despite the "cookies issue", which indeed, makes usual way of reading/replying in forums (open all subscribed threads in new tabs - windows in N900's case - and read/reply to the one by one, closing done ones) much less sexy. I guess that handling cookies between opened windows it is in a to-do list?
BTW, small issue with it - now, when you shift+up/down arrow in text fields (to highlight whole lines), page scrolls at the same time. I think disabling scrolling when shift (or any modifier?) is pressed, might be a good idea.
Also, two issues (small one, and a goddamned big blocker-sized one, in that order) I've noticed: 1. Browsing history (complete one) acts strange. For example, after visiting dozens threads on TMO - all in separate windows - and closing all of them, on next start of QML Browser, my history consists only of main TMO page, and login page. Applies to other sites too, of course. MicroB stores every sub-page (at least when visited in separate windows).
2. The old bane of everything Qt/QML related hit us again. I'm talking, of course, about the fact, that QML Browser completely ignores 80% of special characters binded to hardware keyboard. So, for example, if in your: [/i]/usr/share/X11/xkb/symbols/nokia_vndr/rx-51[/i] ...you have [ mapped to shift + Alt_Gr (aka blue arrow) + f (or anything else, for that matter), it works in whole Maemo (terminal, microB, etc) QML Browser will only detec that you've pressed "-". Same forany other QT/QML program, sadly - but in browser, lack of majority custom-mapped keys is very painful, obviously. If you find a way to fix it, you immediately receive Maemo's Nobel prize Not sure what can be done about it, though (so far, no one was able /knowledgeable enough to fix it - which made me hate QML, for a long while).