View Single Post
marxian's Avatar
Posts: 2,448 | Thanked: 9,523 times | Joined on Aug 2010 @ Wigan, UK
#92
Originally Posted by Estel View Post
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:
Code:
wmctrl -r :ACTIVE: -b toggle,fullscreen
... 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.
I'm not sure of the cause of these fullscreen interface issues. I suspect it's some problem with QWebView that prevents UI updates. I'll have to do some investigation.

Originally Posted by Estel View Post
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.
When I first implemented the cursor mode, I had not finished the QML key handling in the components, so there was no way to handle the shift key press event. The key handling has since been implemented, so I should be able to complete the cursor mode implementation for the next update.

Originally Posted by Estel View Post
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.
It won't be possible to fix rendering issues at the application level. It may be possible to fix them in the components, but I suspect the changes need to be made at a lower level than that exposed in the QtWebKit public APIs.
__________________
'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: