[Bug 27762] [Custom]: Make unresolved state an explicit flag.

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

Dimitri Glazkov (AFK until Jan 5) <dglazkov@chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[Custom]: what happens with |[Custom]: Make unresolved
                   |Unresolved Elements when    |state an explicit flag.
                   |removed from the tree?      |

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

This is this bug.

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

This is bug 27770.

> 
> 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).

This is bug 27768.

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

Received on Tuesday, 6 January 2015 17:24:45 UTC