- From: Addison Phillips via GitHub <sysbot+gh@w3.org>
- Date: Thu, 10 Mar 2022 17:28:31 +0000
- To: public-css-archive@w3.org
aphillips has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-variables] String identity of custom property name should be emphasized == 4.1 Serializing Custom Properties https://www.w3.org/TR/css-variables-1/#serializing-custom-props > Custom property names must be serialized with the casing as provided by the author. > > Note: For non-custom properties, property names are restricted to the ASCII range and are [ASCII case-insensitive](https://infra.spec.whatwg.org/#ascii-case-insensitive), so implementations typically serialize the name lowercased. > > Specified values of [custom properties](https://www.w3.org/TR/css-variables-1/#custom-property) must be serialized exactly as specified by the author. Simplifications that might occur in other properties, such as dropping comments, normalizing whitespace, reserializing numeric tokens from their value, etc., must not occur. Custom property names are not just restricted to the casing provided by the author, but also to the exact code point sequence. Unicode normalization of the name would potentially break matches elsewhere, since the requirement is _identical to_. This is covered for **values** (in the third paragraph above) but this should also be applied to the property name. I would suggest replacing this: > Custom property names must be serialized with the casing as provided by the author. with > Custom property names must be serialized exactly as provided by the author without altering the case or Unicode normalization. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7128 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:28:33 UTC