- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Dec 2023 14:01:49 +0000
- To: public-css-archive@w3.org
From https://github.com/w3c/csswg-drafts/issues/9343#issuecomment-1832665242: > [@tabatkins]: The "extract a value from particular progress along a keyframe'd animation" idea is completely unrelated to mix(); it was discussed around the same time, but it's not in any way a "mixing" function. I'm annoyed it got folded into the spec; it needs to be a completely different function. I suggest ignoring it; I'm pinging Elika right now about killing it (and potentially reviving it in a dedicated function instead). @tabatkins Is your objection mostly towards the re-use of the _name_ `mix()`, or it is something more significant? We're considering a prototype of some of the primitives needed for this use-case, so it would be useful to know how deep this objection goes. -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6245#issuecomment-1845396028 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 7 December 2023 14:01:52 UTC