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

Sat Dec 6 12:31:32 GMT 2003

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dirk Mueller wrote:

> On Saturday 06 December 2003 10:36, Andras Mantia wrote:
> 
>> So, is this patch acceptable?
> 
> Well, I tested with Mozilla and IE and both accept a charset declaration
> also after <body>.
> 
> furthermore there might not be an explicit <body>, for example there could
> be a <frameset> instead.
Indeed.
> 
> I haven't found out yet if the other browsers simply reload the whole
> document when the charset is changing or have some built-in limit (like
> scanning the first X kb in the document or similiar).

I see. Well, the current behavior in KHTML is very strict and fails to find 
out the encoding in some cases. This is why I'm insisting to change and find 
out a solution. Even if it searches only before <body>,<frameset>, </head> is 
a step forward.

Andras

> 
> 
> Dirk

- -- 
Quanta Plus developer - http://quanta.sourceforge.net
K Desktop Environment - http://www.kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE/0cwkTQdfac6L/08RAkrMAKCpPj+SbV8Xpb6oUVYc/bW9v8h6qQCdE/gL
F0TKvwqW/zaYCQG72y/rHdY=
=muvR
-----END PGP SIGNATURE-----