For the avoidance of doubt, we don't block on WG consensus. If there's sufficient evidence that a feature has been developed with high quality and strong developer support, that's enough for us. CSS WG blessing is strictly nice-to-have.
On Tuesday, May 28, 2024 at 4:37:39 PM UTC-7 Emilio Cobos Alvarez wrote: > Sounds good, thanks Tab! > > -- Emilio > > On Tue, May 28, 2024, 22:47 Tab Atkins Jr. <jackalm...@gmail.com> wrote: > >> On Mon, May 27, 2024 at 1:04 PM 'Emilio Cobos Álvarez' via blink-dev >> <blink-dev@chromium.org> wrote: >> > Has this been reviewed by the CSSWG? (not only the PR I mean, but the >> > feature as a whole). The spec PR: >> > https://github.com/w3c/csswg-drafts/pull/9515 >> > >> > Doesn't mention any issue or discussion in a CSSWG call. Usually having >> > a resolution for a new feature is a requirement to get it merged... >> > >> > We recently discussed a similar process mishap in >> > https://github.com/w3c/csswg-drafts/issues/7767, would be good not to >> > repeat it. >> >> The feature was discussed and resolved on back in 6985 >> <https://github.com/w3c/csswg-drafts/issues/6985#issuecomment-1049029573> >> (the issue is originally just about pseudo-classes, but the discussion >> on the call was about snap events as well, and the resolution covered >> that explicitly). We've also discussed some of the features's issues >> in the WG in the last few months. >> >> But since it's been a while since the original resolution, I've gone >> ahead and tagged 6985 with Agenda+ just to give a heads-up to the >> group. (David and flackr will be able to discuss it on the WG call >> next week; I'll be at CSS Day. Or we can talk about it at the f2f in >> two weeks.) >> >> > I see some follow-up issues on naming and such things are still open >> > (though some /do/ have resolutions). Do you plan to update the spec and >> > tests? >> >> The relevant issues have all been resolved, but you're right, only the >> naming one had been editted so far. David's working on the other two >> (bubbling, and pseudo-elements), and we'll get them reviewed and >> merged asap. Thanks for the heads up. >> >> ~TJ >> > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/17bba065-c846-4b5e-ac32-6cd281db8f24n%40chromium.org.
