On Thu, Sep 2, 2021 at 1:18 PM Frédéric Wang <fw...@igalia.com> wrote:
> Le 02/09/2021 à 12:15, Yoav Weiss a écrit : > > > An actual explainer that outlines what the feature does, and its developer > and user benefits would be helpful for reviewing this. > > Just to clarify, the slotchange event is already implemented in all > browsers, one can find document on MDN [1] [2]. But <slot> is used by > developers as a placeholder for custom DOM tree in Web Components and the > slot change event is dispatched when such a substree changes. Typically, > the JS code of the web component will listen to slotchange events and react > with necessary updates. > > As Sonia explained in the motivation, one could just use addEventListener, > but for convenience and consistency with other events (e.g. load) it makes > sense to add a IDL onslotchange attribute... which also reflect the > attribute on elements. And because web components typically put their > contents in a ShadowRoot, it makes sense to be able to place the listener > on that root. > > (note: I'm not really an expert on web components, probably people who are > more familiar can explain better the motivation) > OK, thanks for clarifying what this intent is aiming to ship. > > > >> TAG review >> >> TAG review status >> Not applicable > > > Can you explain why is a TAG review not applicable? > > This is just a small change to an existing spec implemented in browsers > and it was discussed at WHATWG (see the link provided by Sonia). When is a > TAG review typically required? > OK, I agree that since this is following a well-known and established pattern, a TAG review is most-probably an overkill. > > >> >> >> Risks >> >> Interoperability and Compatibility >> >> Gecko: >> Positive (https://bugzilla.mozilla.org/show_bug.cgi?id=1501983) >> >> >> WebKit: >> Shipped/Shipping (https://bugs.webkit.org/show_bug.cgi?id=191310) >> >> >> Incidentally, Sonia landed her patch so this is now shipped in WebKit and > Firefox. > > Web developers: >> No signals > > > Could you gather signals? https://goo.gle/developer-signals > > We were not able to find much information from > https://github.com/whatwg/html/issues/3487 ; I think Sonia meant to use > N/A "The change is too small to justify this effort". > The motivation section brings up use cases that this would make easier, but it's not super clear what they are, and if developers feel they are important. I wondered if this is something you have evidence for. With that said, now that I understand what you're trying to ship, consistency can also be an argument for such a change. > -- > > Frédéric Wang > > -- > 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/ce90f246-e1f9-ce3f-9bcc-efdeca45cb01%40igalia.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ce90f246-e1f9-ce3f-9bcc-efdeca45cb01%40igalia.com?utm_medium=email&utm_source=footer> > . > -- 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/CAL5BFfX06kfvQqd5LQhbg_p6qgSZuQF9fT-GoB-CF9nD35Zn7g%40mail.gmail.com.
