Case sensitivity of element.<attributename>

[David Faure]

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

On Wednesday 06 November 2002 11:47, David Faure wrote:
> Would this be ok?
> -NodeImpl::Id DocumentImpl::attrId(DOMStringImpl* _namespaceURI, DOMStringImpl *_name, bool readonly)
> +NodeImpl::Id DocumentImpl::attrId(DOMStringImpl* _namespaceURI, DOMStringImpl *_name, bool readonly, bool forceCaseSensitive)
> [....]
> 
> A dirtier hack, to avoid any change in khtml itself (and to avoid the more complex logic above)
> would be to set the htmlMode to XHTML before calling attrId, then resetting it back. Hmm.

None of those is enough :(

When _parsing_ the attribute names are replaced with IDs.
So we lose the information of whether the attribute was "foo", "Foo", or "FOO".
I don't see a way to perfectly emulate the IE behaviour here, without getting rid
of this khtml important optimization (attributes replaced with IDs).

We are currently _more_ tolerant than IE, which is unusual :) ... but it's what
breaks 47090 (which is obviously a typo in the script, not an intended use).

I'm considering this one a WONTFIX for now, then.

- -- 
David FAURE, david at mandrakesoft.com, faure at kde.org
http://people.mandrakesoft.com/~david/
Contributing to: http://www.konqueror.org/, http://www.koffice.org/
Get the latest KOffice - http://download.kde.org/stable/koffice-1.2/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9ymV372KcVAmwbhARAiWYAJoCLQQkUiebgvSve+RqKC78ebSyRACePpTb
VFbAJv2I3lUWlOFqBMQnFMU=
=UOfQ
-----END PGP SIGNATURE-----