- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Oct 2022 04:12:41 +0000
- To: public-css-archive@w3.org
Yeah, it gives me a headache each time I try to understand how color serialization is defined. The simple answer is that browsers do not always serialize in a conforming way and I think serialization does not have a high priority, be it for browser interoperability or spec authors. I understand it since it is not a feature for end users. With that said, two people asking the same question may be a sign that the spec can be improved. The part you are linking to defines that a named color is derived from a computed value, but `style.color` (specified value) is not. Why would it be required to serialize a named color as part of a specified value, to `rgb()`? I have learned (this should be defined somewhere, imo) that a specified value is meant to represent the value as specified by its author + simplifications from tokenization (lowercase keywords, etc). Good luck with your WPTs! =) -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7870#issuecomment-1277003229 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 October 2022 04:12:43 UTC