[PATCH] Possible solution to fix #68747 and #66103

Thu Dec 4 13:58:41 GMT 2003

On Tuesday 02 December 2003 13:40, Andras Mantia wrote:

>  Currently KHTML stops parsing the <head> </head> tag area for encoding
> information if an unexpected/invalid tag is found prior of <head> or inside
> <head></head>. This results in not detecting the correct encoding in those
> (broken) files.

which broken files?

> The only drawback I can see is that parsing such pages becomes somewhat
> slower.

"somewhat" is a good one. it will delay parsing and rendering of the whole 
page until it is completely received in almost all cases now. Thats not 
acceptable. 