- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 Jan 2020 15:47:57 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Overlap between the definition of resolving color values and serializing <color> component values.`, and agreed to the following: * `RESOLVED: move serialization into color-4` <details><summary>The full IRC log of that discussion</summary> <stantonm> topic: Overlap between the definition of resolving color values and serializing <color> component values.<br> <astearns> github: https://github.com/w3c/csswg-drafts/issues/982<br> <stantonm> chris: css object model has not clear text about how to construct these color strings<br> <stantonm> ... color-4 should obsolete that part of the model<br> <stantonm> ... do people agree? or do we think it needs serialization<br> <stantonm> ... even if you have rgb with percentage, some bits get thrown away<br> <stantonm> ... should it be in color-4 or OM<br> <stantonm> emilio: as long as its well defined I don't care<br> <stantonm> TabAtkins: prefer color spec<br> <stantonm> leaverou: remove it from css OM and just point to color-4<br> <stantonm> florian: agree, color-4 now has appropriate infomation to represent that spec<br> <stantonm> RESOLVED: move serialization into color-4<br> <stantonm> fantasai: before we remove from OM should we publish it<br> <stantonm> TabAtkins: publish both after the move<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/982#issuecomment-577740386 using your GitHub account
Received on Thursday, 23 January 2020 15:47:59 UTC