- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Fri, 12 Sep 2025 16:55:33 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-2025][css-easing-2] Add `linear()` to Safe to Release exceptions``. <details><summary>The full IRC log of that discussion</summary> <florian> SebastianZ: there was an issue about whether it is in shippable state, and we resolved it is<br> <florian> SebastianZ: implemented across browsers since 2023<br> <florian> SebastianZ: interop is not that high (68%), but we already said it's fine<br> <florian> SebastianZ: just one open issue on github, none in the spec<br> <florian> astearns: the shipable state issue said OK for FPWD, but did not say OK to ship<br> <florian> SebastianZ: Ah, right<br> <florian> SebastianZ: does someone remember if we discussed shipability, or publication only?<br> <florian> astearns: seems we only discussed publishing first<br> <florian> florian: so the precondition is fulfilled, but is the feature good enough?<br> <florian> astearns: test pass rate seems low, I am not OK with putting it in safe to release<br> <florian> astearns: test results show lack of interop<br> <florian> SebastianZ: safe-to-release is supposed to be about spec status, not interop<br> <florian> astearns: editor said it's good<br> <florian> astearns: I'm leaning to not yet<br> <florian> fantasai: the test seems to be largely about specified value, not behavior<br> <florian> fantasai: doesn't seem like a big deal<br> <florian> astearns: I just don't feel confident<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12777#issuecomment-3286071841 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 12 September 2025 16:55:34 UTC