Johannes wrote:
On Thu, Mar 13, 2008 at 10:49:47AM -0400, Jorge Arellano Cid wrote:
Hi,
On Fri, Mar 07, 2008 at 06:17:17AM +0000, place wrote:
This is no sort of proper fix whatsoever, but I was tired of seeing the "would set charset" message. It's actually surprisingly useful for remote files, since they're generally still at the javascript-and-css point at the end of the first packet.
In CVS there is a new approach that restarts parsing the whole page. It works with local/remote files, and page title. Please test it.
Not 100% sure if it's this change, but since recently dillo-fltk loops for me on http://www.ebay.com:
META Content-Type changes charset to: ISO-8859-1 Nav_open_url: new url='http://www.ebay.com/' HTTP Content-Type gave charset as: ISO-8859-1 META Content-Type gave charset as: ISO-8859-1 FltkViewBase::drawTotal META Content-Type changes charset to: Cp1252 Nav_open_url: new url='http://www.ebay.com/' HTTP Content-Type gave charset as: ISO-8859-1 META Content-Type gave charset as: Cp1252 FltkViewBase::drawTotal META Content-Type changes charset to: ISO-8859-1 Nav_open_url: new url='http://www.ebay.com/' HTTP Content-Type gave charset as: ISO-8859-1 META Content-Type gave charset as: ISO-8859-1 FltkViewBase::drawTotal
I should have made it clearer that my little patch from a day ago was intended to fix such looping.