- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Mon, 11 Sep 2023 11:04:38 +0000
- To: public-css-archive@w3.org
> It seems like we want to encourage the use of mix() @mirisuzanne I'm confused. This seems to be the _opposite_ of what this issue originally asked for: > The problems with clamp(), min(), and max() is that you can only interpolate length values on a single property between two points. You may want to interpolate rulesets across multiple breakpoints. It looks to me that `mix()` (and new creative forms of `mix()`) should get their own issues for discussion. > we would want to ensure browsers ship mix() along with any timeline properties. @andruud does that sound right? If container-linked-animations are _useless_ without `mix()`, then yes. (Are they?) > traffic jam This would be solved by additive cascade in the future, right? If yes, this should not be a deciding factor, everything in non-additive CSS is a traffic jam. An at-rule for this seems unnecessarily inconsistent with scroll/view-timeline, but IANAA (I-am-not-an-author), so whatever the group wants. -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6245#issuecomment-1713659075 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 11 September 2023 11:04:40 UTC