- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Sun, 09 Jan 2022 16:39:14 +0000
- To: public-css-archive@w3.org
YES let's please address the use case! As an author I have very frequently been frustrated with this. Out of the ideas proposed above, the one with `<number>` made the most sense to me. I’ll add another idea to the pile, possibly bad but it may help brainstorming. What if we could *invert* the grouping of keyframes and properties, and we could just list the values a given property will go through and have the UA automatically figure out the keyframes, akin to how gradient color stops work? I.e. ``` @keyframes rainbowText { color { values: red; orange; yellow; green; blue; } } ``` Note that this would allow us to do things like: ``` @keyframes rainbowText { color { values: red; orange; yellow; green; blue; } opacity { values: 0; 1; .5; } } ``` without all the annoying math this would require to do with keyframe percentages. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6151#issuecomment-1008332725 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 9 January 2022 16:39:16 UTC