-
Notifications
You must be signed in to change notification settings - Fork 300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dispatching slotchange within a compound microtask #734
Comments
WebKit's code: https://trac.webkit.org/browser/trunk/Source/WebCore/dom/MutationObserver.cpp#L259 I don't think we even implement compound microtask subtask. |
Gecko's code looks pretty similar, but I think not exactly the same if there also some promises around. |
whatwg/html#4437 to investigate removing compound microtasks from HTML. |
Complements whatwg/html#4437. Also clarify which agent the mutation observer microtask queued member is obtained from. Fixes #734.
FYI: based on the HTML PR thread the conclusion here seems to be that we remove the compound microtask infrastructure. This results in a minor simplification of the DOM Standard shown in #741. |
Complements whatwg/html#4437. Also clarify which agent the mutation observer microtask queued member is obtained from. Fixes #734.
HTML requires that "execute a compound microtask subtask" is used to invoke callbacks within a "compound microtask", as I understand it. However, we don't do this for the slotchange event. And it's not clear to me that we can, since dispatching the slotchange event can result in multiple listeners being triggered, each with their own callback. Surely we don't want to weave "execute a compound microtask subtask" through all that?
So how do browsers implement the last step of https://dom.spec.whatwg.org/#notify-mutation-observers today?
cc @whatwg/components
The text was updated successfully, but these errors were encountered: