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: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 3 Oct 2012 11:12:42 -0700
Message-ID: <CAAWBYDCODzMB2ZjUNaZG_UsXjNTN_ku-o8aRp-XZkrpiZnfJWg@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: Fran├žois REMY <fremycompany_pub@yahoo.fr>, www-style@w3.org
On Wed, Oct 3, 2012 at 11:09 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 10/3/12 2:05 PM, Tab Atkins Jr. wrote:
>> But values do the same thing.  @counter-style takes the space of
>> counter style names and mixes in user-defined idents.
> I would have no problems, personally, making the user-defined idents there
> case-sensitive while keeping the built-in counter styles case-insensitive.

The problem is that, as long as we stick with idents, we'd like to
allow overriding the existing styles as well.  Then, again, do we
suddenly make it case-sensitive once the user does it, or do we make
them only override a single casing of the style?

> If we think that would be syntactically weird, we could require that
> user-defined counter styles be strings, not idents.

I don't like this.  We generally force people into strings only when
required - when the necessary name is defined by something besides the
author, so there's no guarantee that it'll match the ident grammar
(and making people remember the ident grammar and use escaping is
painful).  Idents are more convenient (two less characters) and more
consistent with the rest of CSS.

Received on Wednesday, 3 October 2012 18:13:29 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:04 UTC