This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Spec says: > "For each element ELEMENT in TREE whose custom element name is NAME: " In what order? What happens when the various events that fire during this algorithm trigger handlers that mutate TREE? This thing needs to be very clearly defined. As a start, I would recommend not firing any events until after all the other work is done.
(In reply to comment #0) > Spec says: > > > "For each element ELEMENT in TREE whose custom element name is NAME: " > > In what order? Good point, needs to be in tree order. What happens when the various events that fire during this > algorithm trigger handlers that mutate TREE? Can you help me understand what you mean here? The algorithm does suppress observers currently (although this might not be the right thing). Which other events are you talking about it? > > This thing needs to be very clearly defined. As a start, I would recommend > not firing any events until after all the other work is done. If you're talking about elementreplace and elementupgrade events, I don't see any harm in them being fired after each upgrade?
> Which other events are you talking about it? Mutation events, for one thing. But also, suppressing mutation observers may well not be ok. See the separate bug filed on that. But most importantly, the elementreplace and elementupgrade events. > I don't see any harm in them being fired after each upgrade? Let me re-ask: What happens when the various events that fire during this algorithm trigger handlers that mutate TREE?
The spec has been updated to address this a while back.