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

Re: [css-variables] editorial nits/suggestions

From: John Daggett <jdaggett@mozilla.com>
Date: Wed, 27 Feb 2013 16:24:57 -0800 (PST)
To: www-style list <www-style@w3.org>
Message-ID: <692274617.5611563.1362011097472.JavaMail.root@mozilla.com>
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.

Received on Thursday, 28 February 2013 00:25:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:26 UTC