I was recently in an environment with a very weak connection. With most sites, if I didn't get a full page, lsof would show the connection still open and just sitting there. Some sites _would_ close the connection, but unfortunately dillo wouldn't give the user any indication that further waiting was pointless. I just committed some code that aborts the connection on read failure. It also gives a status msg to the user (though status messages are imperfect, as discussed last month). The case where no data was received could bear further improvement, but I had limited time and improved what I needed most. It got a week or so of "free" testing in that bad environment, and hasn't given me any trouble since then in more solid environments.
Hi, On Sat, Apr 09, 2016 at 04:25:29PM +0000, eocene wrote:
I was recently in an environment with a very weak connection. With most sites, if I didn't get a full page, lsof would show the connection still open and just sitting there. Some sites _would_ close the connection, but unfortunately dillo wouldn't give the user any indication that further waiting was pointless.
I just committed some code that aborts the connection on read failure. It also gives a status msg to the user (though status messages are imperfect, as discussed last month).
The case where no data was received could bear further improvement, but I had limited time and improved what I needed most.
It got a week or so of "free" testing in that bad environment, and hasn't given me any trouble since then in more solid environments.
Do you mean the problem of "unresponsive links" doesn't happen anymore on "solid" environments? -- Cheers Jorge.-
I have noticed that Dillo doesn't render px properly - this snippet: <hr width=500px align=left> just produces: . Using 50% (e.g.) works OK. Is this bad HTML or a 'to-do' thing? BTW, great bit of kit - so fast... Nick -- Gosh that takes me back... or is it forward? That's the trouble with time travel, you never can tell." -- Doctor Who "Androids of Tara"
On So, Apr 10, 2016, Nick Warne wrote:
I have noticed that Dillo doesn't render px properly - this snippet:
<hr width=500px align=left>
just produces:
.
Using 50% (e.g.) works OK. Is this bad HTML or a 'to-do' thing?
The HTML width attribute (which is depricated, btw) does not support "px", instead, <hr width=500 ...> would be correct. Sebastian
On 10/04/16 16:21, Sebastian Geerken wrote:
On So, Apr 10, 2016, Nick Warne wrote:
I have noticed that Dillo doesn't render px properly - this snippet:
<hr width=500px align=left>
just produces:
.
Using 50% (e.g.) works OK. Is this bad HTML or a 'to-do' thing?
The HTML width attribute (which is depricated, btw) does not support "px", instead, <hr width=500 ...> would be correct.
Yes, thanks, I just sussed that out. Dillo is great for debugging HTML, as most browsers somehow parse crappy input into what seems right (but is wrong!). width=475 works great now. Thanks, Nick -- Gosh that takes me back... or is it forward? That's the trouble with time travel, you never can tell." -- Doctor Who "Androids of Tara"
participants (4)
-
eocene＠gmx.com -
jcid＠dillo.org -
nick＠linicks.net -
sgeerken＠dillo.org