[Bug 27762] [Custom]: what happens with Unresolved Elements when removed from the tree? from bugzilla@jessica.w3.org on 2015-01-06 (public-webapps-bugzilla@w3.org from January 2015)

From: <bugzilla@jessica.w3.org>
Date: Tue, 06 Jan 2015 17:04:42 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-27762-2532-UjARQTmmzH@http.www.w3.org/Bugs/Public/>

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

--- Comment #5 from Dimitri Glazkov (AFK until Jan 5) <dglazkov@chromium.org> ---
Specifying this explicitly as a flag SGTM.

Honing wording in the element upgrade algorithm to better highlight the fact
that the element queue is indeed cleared (see step 4) SGTM too.

Also need to make the adding to the upgrade candidates map an explicit step
during instantiation. This would help with explaining how the unresolved type
extensions end up in the upgrade candidates map (so that we don't have to store
the value of the "is" attribute).

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

Received on Tuesday, 6 January 2015 17:04:46 UTC