- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 10 Mar 2025 21:34:17 +0000
- To: public-css-archive@w3.org
> I’m not sure interactivity is ready to be marked "safe to release” anyway, as the TAG is currently working on their https://github.com/w3ctag/design-reviews/issues/1055#issuecomment-2695910757, and I see from the [intent thread](https://groups.google.com/a/chromium.org/g/blink-dev/c/O5ZmbyRh9LE/m/cqwaZmbaAQAJ) that it’s been shipped with promises to “invest in additional changes as necessary” This is the exact sort of chicken-and-egg I'd like to *avoid*, by not invoking even more cross-WG bureaucracy. Different WGs and standards bodies can have different goalposts for various steps, and linking them implicitly unions all the goalposts, making it harder to finish things without anyone being "responsible" for the slowdown. The WHATWG's standard for when something is safe to merge has for some time been "multi-implementor interest". That's a fairly easy bar to clear; you just need a public signal saying "yes". The CSSWG's bar for putting something in the "safe to release" section of the snapshot has never been firmed up (due to lack of any real need), but responses like this from Alan (which I don't think are unreasonable!) show that this bar is definitely *different* to the WHATWG's "multi-implementor interest", and generally *higher*. We, the CSSWG, should not be approving the WHATWG hooking themselves to us like this unless the WHATWG indicates that they do indeed, affirmatively, want to increase the standards they apply to things being mergeable. To the best of my knowledge, they *don't* want that, so this looks to me like people just trying to squint and find equivalent-looking things without really considering the ways in which they're not equivalent. All the implementors in the WHATWG have coworkers in the CSSWG. They can ask *them* for stability. We don't need to give them a stamp of stability, either slowing down the WHATWG working mode or relaxing the CSSWG's desired requirements. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11863#issuecomment-2711899634 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 10 March 2025 21:34:18 UTC