[whatwg] [html5] r4949 - [giow] (0) The CSS rules need to do attribute value matching consistently across [...]
L. David Baron
dbaron at dbaron.org
Sun Aug 29 06:01:27 PDT 2010
On Wednesday 2010-08-25 10:28 +0200, Anne van Kesteren wrote:
> On Wed, 25 Aug 2010 09:44:34 +0200, Christoph Päper
> <christoph.paeper at crissov.de> wrote:
> >I for one would expect that selector to match that element,
> >although I would never write HTML like that. Imagine a browser or
> >user stylesheet where you would effectively have to list all
> >possible casings.
> 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.
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
More information about the whatwg