- From: Bramus via GitHub <noreply@w3.org>
- Date: Mon, 16 Jun 2025 10:32:16 +0000
- To: public-css-archive@w3.org
With this [soon shipping in Chrome](https://chromestatus.com/feature/5112558941634560) and also [announced as part of Safari 26](https://webkit.org/blog/16993/news-from-wwdc25-web-technology-coming-this-fall-in-safari-26-beta/#:~:text=in%20CSS.-,Progress%20function,-Safari%20beta%20adds) maybe we should get a resolution on the clamping behavior? I don’t enough experience to decided on whether it should clamp by default or not, but reading the comments here _(and drawing parallels to [`overallProgress`](https://drafts.csswg.org/web-animations-2/#the-overall-progress-of-an-animation))_ perhaps it should? [Tab’s suggestion to add a `clamp` keyword](https://github.com/w3c/csswg-drafts/issues/11825#issuecomment-2964403863) also seems like a viable and easy to achieve route, but OTOH the same can be said for adding an `unclamped` keyword if the function were to clamp by default. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11825#issuecomment-2976018907 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 16 June 2025 10:32:17 UTC