[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 #1 from Dimitri Glazkov <dglazkov@chromium.org> ---
(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?

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

Received on Saturday, 12 January 2013 00:38:18 UTC