- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Jul 2021 13:49:48 +0000
- To: public-css-archive@w3.org
svgeesus has just created a new issue for https://github.com/w3c/csswg-drafts: == Pernicious links to CSS-COLOR-3 for `<color>` == Despite my best efforts: ```html <pre class='ignored-specs'> spec:css-color-3 spec:css3-color </pre> <pre class=link-defaults> spec:css-color-4; type:dfn; text:color spec:css-color-4; type:value; text:color spec:css-color-4; type:value; text:currentcolor spec:css-color-4; type:property; text:color </pre> ``` (the above being sufficient to stop Color 5 linking to Color 3) CSS specs will link to CSS Color 4 for the `currentColor` value and the `color` property **BUT stubbornly assert that `<color>` is defined in CSS Color 3**. This is a significant problem because the syntax for the `<color>` type is significantly expanded in CSS Color 4. Plus, CSS Color 4 defines resolving color values, and serializing color values (moved here from CSSOM). I notice that some specs attempt to clarify this in prose. For example [css-ui-4 definition of `outline-color`](https://drafts.csswg.org/css-ui-4/#propdef-outline-color): > <html><body> <!--StartFragment--> Computed value: | The computed value for invert is invert. For <color> values, see [[!CSS-COLOR-4#resolving-color-values]] in [CSS-COLOR-4]. -- | -- <!--EndFragment--> </body> </html> and yes ... `<color>` links to CSS Color 3. Is there some magical link-defaults incantation that I am missing, or ![1o9ejc](https://user-images.githubusercontent.com/2506926/125086946-c18f1380-e0d4-11eb-84b9-b835c3309706.jpg) Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6436 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 9 July 2021 13:49:51 UTC