- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Mon, 9 Jun 2014 17:34:01 -0700
- To: "Phillips, Addison" <addison@lab126.com>
- Cc: "CSS WWW Style (www-style@w3.org)" <www-style@w3.org>, "www-international@w3.org" <www-international@w3.org>
On Thu, May 29, 2014 at 12:41 PM, Phillips, Addison <addison@lab126.com> wrote: > Hello CSS, > > I am forwarding the following issue on: > > http://www.w3.org/TR/css-variables-1/ > > This issue is a personal comment, as the I18N WG has not had an opportunity to consider it yet. > > === > > Section 2 says in part: > > <quote> > Unlike other CSS properties, custom property names are case-sensitive. > > EXAMPLE. While both --foo and --FOO are valid, they are distinct properties - using var(--foo) will refer to the first one, while using var(--FOO) will refer to the second. > </quote> > > Case sensitivity is not the only variation that can apply to text. While citing the case sensitivity is useful, should mention be made of other variations, such as Unicode Normalization? I believe that the actual restriction is that the text must be identical. The reason I called that one out specifically is because normal CSS properties are ASCII case-insensitive. The behavior of custom properties is identical to normal properties wrt normalization. You can observe this with some forms of normalization, as we don't canonicalize any of the ASCII-equivalent codepoints to ASCII. Of course, talking just of NFC vs NFD vs nothing, you can't tell the difference, since normal properties don't have any relevant codepoints. ~TJ
Received on Tuesday, 10 June 2014 00:34:50 UTC