W3C home > Mailing lists > Public > www-style@w3.org > October 2012

Re: [css3-fonts][css-variables][css-counter-styles-3][css3-values] Case sensitivity of user-defined identifiers

From: Brian Kardell <bkardell@gmail.com>
Date: Mon, 1 Oct 2012 09:11:06 -0400
Message-ID: <CADC=+jdamWczzT4Mcbd+aDh6VYHeRR+f_zXck__WM2vkjW_pAg@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: www-style@w3.org
Brian Kardell :: @bkardell :: hitchjs.com
On Sep 30, 2012 11:15 PM, "Boris Zbarsky" <bzbarsky@mit.edu> wrote:
>
> On 9/30/12 10:59 PM, John Daggett wrote:
>>
>> However, lookups done using document.getElementById are case
*insensitive*.
>
>
> They sure shouldn't be!  Where are he case insensitive?
>
>
>> So I think we should stick with (1) and not try to create new additional
casing
>> rules.  I'm not suggesting this is ideal but I think the "ideal" way of
using
>> normalization and full case mapping needs to first be addressed in a
web-wide way
>> rather than just within CSS.
>
>
> For what it's worth, the "case insensitive" parts of HTML use ASCII case
insensitivity.  But they only apply to a limited set of identifiers. For
anything where user-provided stuff is used, HTML is case-sensitive.  An
exception is quirks mode, where some things like id and class matching for
CSS are ASCII case-insensitive.
>
> And I think (1) would be fine by me.
>
> -Boris
>

Given everything else existing (learned a few new things myself here thanks
to tab and borris) it seems that #1 is both easier and least surprising,
despite limitations, that seems like a win to me.
Received on Monday, 1 October 2012 14:27:55 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:01 GMT