[Bug 20491] [Custom]: Need to actually define the upgrade algorithm so it's interoperably implementable

https://www.w3.org/Bugs/Public/show_bug.cgi?id=20491

--- Comment #2 from Boris Zbarsky <bzbarsky@mit.edu> ---
> 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?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Saturday, 12 January 2013 01:08:22 UTC