Next steps for the Blink launch process
Reach out to a spec mentor
Consider showing your draft intent email to your spec mentor or sending it to spec-mentors@chromium.org. They can help make sure that your intent email is ready for review.
Copy and send this text for your "Intent to ..." email
Email to
Subject
Body
Contact emails
ssingla@igalia.com, fwang@chromium.orgExplainer
NoneSpecification
https://html.spec.whatwg.orgSummary
The slotchange event is fired on a <slot> element when the node(s) it contained change. One can listen to that event via the EventTarget.addEventListener() API. The goal is now to expose the onslotchange IDL attribute from the GlobalEventHandlers and ShadowRoot interfaces, so that one can register a listener by attaching this attribute to target elements.
Blink component
Blink>DOMMotivation
The slotchange event is fired on a <slot> element when the node(s) it contained change. One can naturally listen to that event via the EventTarget.addEventListener() API. However, web developers are also familiar with the alternative attribute-based form (e.g. element.addEventListener("load", ...) Vs on <element onload="...">) which is sometimes convenient for quick testing. For consistency with other events, an attribute onslotchange is thus added.
Initial public proposal
TAG review
TAG review status
Not applicableRisks
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)
Web developers: No signals
Debuggability
No DevTools changes are required, treated like any other event/attribute.