- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 03 Sep 2025 15:32:58 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-2025][css-will-change-1] Add CSS Will Change 1 to Reliable CRs`. <details><summary>The full IRC log of that discussion</summary> <emeyer> SebastianZ: will-change has very high interop in main engines; 12 open issues, with 8 substantial, zero open issues in the spec<br> <emeyer> …propose to move to Reliable CR<br> <emeyer> florian: I suspect that’s possiblke but I’m concerned that it’s under-maintained because it hasn’t been looked at in a while<br> <emeyer> …We haven’t been actively thinking about the open issues<br> <emeyer> …Would like assurance from someone who’s worked on this more directly<br> <emeyer> astearns: I’m concerned about the number of issues, but not having looked at them, I don’t konw if they’re for the next level or not<br> <emeyer> florian: Skimming, some seem like interop, but there might be de facto interop<br> <emeyer> …We could probably get there, but not having looked at the spec in three years, I don’t know how much effort it would take to find out<br> <emeyer> astearns: Shall we close no change?<br> <emeyer> florian: Can we punt and come back when Tab can give input?<br> <TabAtkins> Note: I cannot answer those questions right now, it's been a few years since I've had to work on it.<br> <emeyer> …The ED is as old as the TR draft<br> <emeyer> astearns: Let’s take no resolution and come back to it<br> <ChrisL> q+ to wonder who the real editors of MQ5 are<br> <emeyer> SebastianZ: That works for me<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12691#issuecomment-3249748122 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 September 2025 15:32:59 UTC