W3C home > Mailing lists > Public > public-css-archive@w3.org > December 2019

[csswg-drafts] [css-color] Be more explicit that color names are *ASCII* case-insensitive (#4599)

From: Frédéric Wang via GitHub <sysbot+gh@w3.org>
Date: Fri, 13 Dec 2019 10:52:44 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-537481617-1576234363-sysbot+gh@w3.org>
fred-wang has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-color] Be more explicit that color names are *ASCII* case-insensitive ==
From the CSS color spec: 
* "As usual for CSS-defined idents, all of these keywords are case-insensitive." ( https://drafts.csswg.org/css-color/#named-colors )
* "Note: As with all other keywords, these names are case-insensitive. They are shown here with mixed capitalization for legibility."  ( https://drafts.csswg.org/css-color/#css-system-colors )
* " Only later did CSS pick it up, at which point the capitalization stopped mattering, as CSS keywords are case-insensitive." ( https://drafts.csswg.org/css-color/#currentcolor-color )

However, the CSS value spec says pre-defined keywords are ASCII case-insensitive:  

Concretely, ftp://ftp.unicode.org/Public/UNIDATA/CaseFolding.txt has this line:

    017F; C; 0073; # LATIN SMALL LETTER LONG S

which means that `ſilver` is case-insensitively equal to `silver`. However, it is not ASCII case-insensitively equal to `silver` (only a-z <-> A-Z equivalence are considered in that case).

Blink, Webkit and Gecko seems to treat colors as ASCII case-insensitive.

Note: I'm opening this for the color spec, but it is probably worth checking that for other CSS specs too.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4599 using your GitHub account
Received on Friday, 13 December 2019 10:52:46 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:57 UTC