- From: Addison Phillips via GitHub <sysbot+gh@w3.org>
- Date: Thu, 10 Mar 2022 17:52:04 +0000
- To: public-css-archive@w3.org
aphillips has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-variables] strengthen advice on string identity == Defining Custom Properties: the [--*]() family of properties https://www.w3.org/TR/css-variables-1/#defining-variables > Different OSes or input methods can sometimes output visually-identical text with different codepoints, so authors should be aware of this potential hazard. This relates to this requirement: > Unlike other CSS properties, custom property names are not [ASCII case-insensitive](https://infra.spec.whatwg.org/#ascii-case-insensitive). Instead, custom property names are only equal to each other if they are [identical to](https://infra.spec.whatwg.org/#string-is) each other. In Example 2, the spec calls out that the term *identical to* refers to the underlying Unicode code points. The advice to authors could be stronger here. To the above consider adding guidance such as: > Operating systems, keyboards, or input methods sometimes encode visually-identical text using different codepoint sequences. Authors are advised to choose variable names that avoid potential confusion or to use escapes and other means to ensure that similar appearing sequences are identical. See [Section 2.3](https://www.w3.org/TR/charmod-norm/#normalizationLimitations) in [CHARMOD-NORM] for examples. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7133 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 10 March 2022 17:52:05 UTC