- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Nov 2021 17:28:37 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-values] define parse-time value aliasing`, and agreed to the following: * `RESOLVED: Accept edits, expand to allow aliased functions` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: [css-values] define parse-time value aliasing<br> <chris> miriam: is the changes section up to date?<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/6193<br> <emilio> scribenick: emilio<br> <fantasai> fantasai: Added value aliasing section to cascade-4/5<br> <fantasai> emilio: Weird that it is scoped to keywords<br> <fantasai> fantasai: We didn't see any examples of not keywords, but could certainly reword to be more general<br> <emilio> emilio `-webkit-image-set()`-> `image-set()`<br> <emilio> Same with a bunch of gradient functions<br> <chris_> rrsagent, here<br> <RRSAgent> See https://www.w3.org/2021/11/17-css-irc#T17-27-14<br> <fantasai> fantasai: So functions and keywords, anything else?<br> <fantasai> s/scribenick: emilio//<br> <emilio> I don't _think_ so of the top of my head<br> <fantasai> astearns: So proposed to take edits, with additional change to add functions<br> <fantasai> fantasai: sgtm<br> <emilio> emilio: sgtm<br> <fantasai> RESOLVED: Accept edits, expand to allow aliased functions<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6193#issuecomment-971798557 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 November 2021 17:28:38 UTC