- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Jun 2022 16:54:03 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-color-5] What should the behavior of the CSS Color 5 color functions be when passed currentcolor as <color>`, and agreed to the following: * `RESOLVED: specified style maintains calculations, computed style computes everything as far as possible (but maintains currentColor's identity), resolved color resolves through to absolute color` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: [css-color-5] What should the behavior of the CSS Color 5 color functions be when passed currentcolor as <color><br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/6168<br> <astearns> ack chris<br> <fantasai> chris: I think we solved this in the issue, iterated the text with emilio<br> <fantasai> emilio: for context with the group, it behaves like calc() - doesn't go away in specified style<br> <fantasai> emilio: goes away in computed style if possible, but preserves currentColor<br> <fantasai> emilio: but this is only observable in typedOM because getComptedStyle returns resolved colors<br> <fantasai> RESOLVED: specified style maintains calculations, computed style computes everything as far as possible (but maintains currentColor's identity), resolved color resolves through to absolute color<br> <fantasai> chris: I believe this also resolves item 5 on the agenda,<br> <fantasai> https://github.com/w3c/csswg-drafts/issues/7302<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6168#issuecomment-1156711756 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 June 2022 16:54:04 UTC