W3C home > Mailing lists > Public > www-style@w3.org > February 2013

Re: [css-variables] editorial nits/suggestions

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 28 Feb 2013 12:16:05 -0800
Message-ID: <CAAWBYDAzgzft8+A+noDKKEVgiHpE09C2BkC10qe8OuF=zk21xA@mail.gmail.com>
To: John Daggett <jdaggett@mozilla.com>
Cc: www-style list <www-style@w3.org>
On Wed, Feb 27, 2013 at 4:24 PM, John Daggett <jdaggett@mozilla.com> wrote:
> Tab Atkins wrote:
>> >> Unlike other CSS properties, custom properties are case-sensitive.
>> >
>> > I think you want to say "custom property names are
>> > case-sensitive", since the values of these properties remain
>> > case-insensitive as per general CSS property values.
>>
>> Actually, the values should stay case-sensitive as well - they're
>> all user-defined idents and the like, after all.  When substituted
>> into a normal property, we stop caring about case, of course.
>
> Hmm, ok, I see what you're getting at.  But saying "custom properties
> are case-sensitive" still feels a bit off, there's no case matching
> going on with the value, all you're saying is that the property name
> is case-sensitive *and* the token stream representing the value is
> preserved as defined, including the casing.

Makes sense.  I've changed the offending sentence to only talk about
property names, and then added a short paragraph slightly further down
about the value of a custom property retaining its author-provided
casing.

~TJ
Received on Thursday, 28 February 2013 20:16:52 GMT

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