- From: Anne van Kesteren <annevk@opera.com>
- Date: Mon, 30 Aug 2010 14:28:57 +0200
On Sun, 29 Aug 2010 15:01:27 +0200, L. David Baron <dbaron at dbaron.org> wrote: > On Wednesday 2010-08-25 10:28 +0200, Anne van Kesteren wrote: >> We need a feature for case-insensitive matching in Selectors already >> for XHTML (if we really care about this, not sure we do). > > Allowing case-insensitive matching beyond matching of a fixed set of > ASCII-only values seems scary. > > If such a general selectors feature were defined as ASCII-only, then > it would appear to work but then break for cases where it needed to > be more than ASCII-only (or where the standard ASCII-only algorithm > is incorrect, such as Turkish, where where I/i are not > case-equivalents; ?/i and I/? are). > > If it weren't ASCII-only, it would involve significantly more > complexity than what's needed to support HTML. I think it can be ASCII-only. You "need" it for input[type=password] and such. The only attributes that are currently "compatibility caseless" are name on <input type=radio> and name on <map>. -- Anne van Kesteren http://annevankesteren.nl/
Received on Monday, 30 August 2010 05:28:57 UTC