23163 2013-09-05 03:50:32 +0000 [Shadow]: Clarify handling of mutation events 2013-10-22 06:54:33 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified All All RESOLVED DUPLICATE 23577 P2 normal --- 1 yutak dglazkov bugs ojan public-webapps-bugzilla oldest_to_newest 93021 0 yutak 2013-09-05 03:50:32 +0000 Section 7 reads: """ The mutation event types must never be dispatched in a shadow tree. """ ... but this statement looks unclear on what it really means in terms of its formal requirements. Specifically: - What should UAs do if a mutation event occur within a shadow tree? - UAs must not "dispatch" the event, in a sense defined in <http://dom.spec.whatwg.org/#dispatching-events>? - Or, UAs must not "invoke" the event? - Either way, we'll need to monkey-patch the DOM events spec to define a desired behavior precisely. - First of all, why do we need to special-case the mutation events? Is there known cases where mutation events interact badly with shadow trees? 93036 1 bugs 2013-09-05 11:05:44 +0000 We're trying to get rid of MutationEvents so we should try to not expose them in new contexts. (And none of the current browser engines implement all the MutationEvents anyway). 93065 2 ojan 2013-09-05 17:34:44 +0000 +1. Lets not fire MutationEvents at all from shadow trees. FWIW, we're slowly removing existing MutationEvent support from Blink as usage gets low enough. 95070 3 yutak 2013-10-22 06:54:33 +0000 Yeah, I'm aware that we are trying to kill MutationEvents and I'm okay with not handling the mutation events. With that said, I think the remaining issue here boils down to defining the exact behavior of event dispatching in general. For now, I'm resolving this bug as a duplicate of bug 23577, which more or less covers the same topic. *** This bug has been marked as a duplicate of bug 23577 ***