On Tue, Aug 18, 2009 at 08:42:28PM -0400, Jorge Arellano Cid wrote:
On Thu, Aug 13, 2009 at 09:43:22PM +0200, Johannes Hofmann wrote:
On Wed, Aug 12, 2009 at 09:54:49PM -0400, Jorge Arellano Cid wrote:
On Mon, Aug 10, 2009 at 12:42:05PM +0000, corvid wrote:
Jorge wrote:
[...] All of these should be working now. Please report any further problem you find. I'll try to make the empty cache entries removal now, and then look for a way to hook the concurrent connection limit without memory leaks.
I don't know whether it's a problem, but I just noticed a difference in behaviour in that my form testcase that submits to localhost (there's no server listening) only prints "submitting multipart/form-data!" and I have to press stop to get '** WARNING **: IO_write, closing with pending data not sent' and see the query.
Yes, I'm yet to look into it.
BTW, just committed a patch for an elusive bug. Now it's possible to browse (& populate DNS cache), disconnect, click a link, have the abort operation on no network condition, reconnect and click it again (and it will work!).
The only bit missing is how to make the link return to its normal color. a_Nav_repush() can do it easily but looks like an overkill. Maybe Johannes has a good idea on this?
Not sure why it should change it's color. It's still a visited link after all.
AFAIS: clicked, not visited! (it was clicked and aborted before the data stream came in).
True. Perhaps we could change the link color to "visited" only after first data has arrived? Then we would not need to undo it on abort.
Or does the link color have another semantics (like page is in cache) in dillo?
Currently, it means exactly that: "page is in cache". That's why our FAQ links appear in visited color: http://www.dillo.org/FAQ.html
If there's a good reason to change it, it should be simple. I see little difference for broadband users; dialup users may like the hint of what's available without connection. No strong feelings on this.
Anyway, the real solution would need the DOM-tree which is currently not available. The DOM-tree would also be needed for :hover, :active, and for Javascript. However we could add a hack similar to the one to compute html->visited_color in Html_tag_open_body(). It assumes that there is just one visited_color in the whole page.
Maybe a repush is not as bad a solution after all. ;)
I'd like to try the DOM-thing. It's not very complicated, but it will use some memory on large pages.
BTW, I hope you're comfortable in your new flat.
Yes, thanks. We're slowly getting back to normal :) Cheers, Johannes