![]() |
Re: WebKit engine for default browser
First, this is incredible and I'd like to profusely thank pronvit for the great work. Browsing on the tablet at this speed is amazing; switching back to gecko makes me want to bang my head against the wall it's so slow. I'm definitely using this as my primary browser.
That said, in gconf the available settings appear to be Quote:
Also, before I started monkeying with gconf, using kinetic scrolling was beautiful and perfect, but now it seems to not cache offscreen areas of the page (i.e. until scroll stops moving, all that appears in the newly exposed region is a finely tiled image of whatever used to be on the bottom of the screen). This behavior continues even after resetting all gconf keys. Any idea why this happens or how to fix it? Thanks again pronvit for all your hard work -- this is by far one of the best enhancements I've come across for the NITs EDIT: Hmm, this didn't work the first time, but a reboot after --recursive-unset appears to have fixed the problem, and now I am able to set scrollbars=0 and kscrollfading to 0.95, which are IMO ideal. This is awesome. |
Re: WebKit engine for default browser
Quote:
|
Re: WebKit engine for default browser
I installed webkit-eal from the garage page a few days ago on my n800 running diablo, and although I can open local pages it crashes every time I try to access a webpage. What kind of debug info can I give to help?
|
Re: WebKit engine for default browser
crazy question but how can I tell if the default browser is using webkit?
Ive followed the only obvious install instructions on post 133 but cant see anything alter. |
Re: WebKit engine for default browser
Just go to http://acid3.acidtests.org : if the score is around 94, your are using webkit !
|
Re: WebKit engine for default browser
also, when a page loads, the loading bare will show percentage, not number of elements downloaded.
oh, and if webkit crashes for some reason, browserd will reload the page in microb, and continue to use that until all browser windows are closed. another way to see if your using webkit is the frame around tapped links. in webkit it will barely be visible, but in microb its a solid frame. and i think by default the start page on a empty browser window is different in webkit also. now, i would love for the selector app to use radio buttons and a ok button rather then the drop down list it uses right now. that or have the drop down list show the currently used engine when started. |
Re: WebKit engine for default browser
Quote:
|
Re: WebKit engine for default browser
Whoa... this is impressive! Installed the deb, rebooted, and I'm flying where I used to crawl!
|
Re: WebKit engine for default browser
luck indicated that the tearing issues could be that webkit is redrawing the page faster then the lcd can fully update.
maybe something to look at for a more smooth experience? |
Re: WebKit engine for default browser
Having used this awesome webkit package for a while now I thought I would post what I have noticed. I am not posting all the amazing good things because they have already been pointed out.
First I would recommend radio buttons, or icons for the engine chooser as tso mentioned above. Second, I noticed that it does not respond to hardware buttons initially. I usually just minimise and then restore and then it will. Third, there are still issues with the thumb keyboard. When typing this post, a return closed the keyboard instead of sending me to the next line. There was one other thing that has slipped my mind. If i think of it i will post it here. Overall i am very impressed. If downloading worked i think it would eliminate my need to ever change the engine back to microb. Hope this is helpful and keep up the good work! |
All times are GMT. The time now is 12:14. |
vBulletin® Version 3.8.8