![]() |
2009-03-16
, 17:58
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#362
|
![]() |
2009-03-16
, 18:33
|
Posts: 87 |
Thanked: 98 times |
Joined on Oct 2007
@ Austria
|
#363
|
the crashes would not be so bad, if it only loaded webkit rather then a partially broken microb (iirc).
![]() |
2009-03-16
, 18:56
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#364
|
![]() |
2009-03-16
, 19:10
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#365
|
You mean it uses the microb engine, ignoring the setting in the browser engine chooser? This happens sometimes, restarting the browser daemon (as root) helps:
/etc/init.d/tablet-browser-daemon restart
![]() |
2009-03-16
, 19:14
|
Posts: 542 |
Thanked: 117 times |
Joined on Sep 2008
@ 52 N, 6 E
|
#366
|
![]() |
2009-03-16
, 20:03
|
Posts: 87 |
Thanked: 98 times |
Joined on Oct 2007
@ Austria
|
#367
|
no, iirc, sometimes the the webkit engine would crash (say thanks to the stop button issue) but then browserd would recover without the browser window closing.
but then it would use microb rather then webkit, and would have some odd input issues that i do not recall the specifics off, sadly...
interesting, i just tried to follow a link, then stop the browser before a connection was made (the tablet was disconnected from wifi), end result, it stopped fine, the connection came up then it tried to download the page, only to crash the whole browser window...
The Following 2 Users Say Thank You to hns For This Useful Post: | ||
![]() |
2009-03-17
, 07:54
|
Posts: 542 |
Thanked: 117 times |
Joined on Sep 2008
@ 52 N, 6 E
|
#368
|
![]() |
2009-03-17
, 08:28
|
Posts: 87 |
Thanked: 98 times |
Joined on Oct 2007
@ Austria
|
#369
|
![]() |
2009-03-17
, 10:55
|
Posts: 542 |
Thanked: 117 times |
Joined on Sep 2008
@ 52 N, 6 E
|
#370
|
Cookies are working for me, but you are right, they don't seem to work on that calculator page. It may be an issue with script-generated cookies (vs. server generated ones). I can't find a setting for this in WebKit, but I'll look into it.
<!-- saved from url=(0014)about:internet --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title>cookie test</title> </head> <body> <script type="text/javascript"> function getcookievalue(name) { var ind; name += '='; str = document.cookie; if ((ind = str.indexOf(name)) != -1) { var end = str.indexOf(';', ind); if (end == -1) end = str.length; str = str.substr(ind+name.length, end-ind-name.length); str = unescape(str); return str; } return ''; } function setcookievalue(name, value) { name += '='; var expDays = 100; var exp = new Date(); exp.setTime(exp.getTime() + (expDays*24*60*60*1000)); var expire = '; expires=' + exp.toGMTString(); var str = name + escape(value) + expire; document.cookie = str; } alert(getcookievalue('test')); setcookievalue('test', new Date()); </script> </body> </html>
![]() |
Tags |
browser, webkit |
Thread Tools | |
|
And the accumulated list of changes since pronvit's 0.0.9 release:
Unfortunately, I couldn't figure out the stop button crashes so far. If you press the stop button after the first bytes of a page have been read but before the main resource is fully loaded, the engine is pretty likely to crash. I can't reproduce this with Tear, so it must be something with the webkit-eal code. I'm having a hard time debugging browserd in a meaningful way, any help is greatly appreciated.
Apart from the stop button, the code is pretty stable for me now, so I guess the next release will be a more official 0.0.11. Just remember to restart the browser daemon or reboot your tablet if you upgrade from pronvit's package or get any strange behaviour, and let me know how this is working for you.
Last edited by hns; 2009-03-17 at 19:30.