This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22455 - [Custom]: Consider inserting unresolved elements at the start of the map.
Summary: [Custom]: Consider inserting unresolved elements at the start of the map.
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 14968
  Show dependency treegraph
 
Reported: 2013-06-25 14:58 UTC by Dominic Cooney
Modified: 2013-06-25 20:47 UTC (History)
0 users

See Also:


Attachments

Description Dominic Cooney 2013-06-25 14:58:19 UTC
"Whenever an unresolved element is created, it must be added to the upgrade candidates map."

It would be good to clarify what order is implied here. Does "added" mean "added to the end of a list"?

Consider three hypothetical fragments of markup A B C that are each markup for a custom element, and a script S which registers the custom elements in ABC.

If the document is structured SABC then the ready callbacks are delivered in order CBA per Section 7 ("Place ... at the front of the ... queue.")

However if the document is structured ABCS then the order in which the ready callbacks are delivered is unclear, but it is presumably ABC.

Is this interpretation correct? Is this seeming inconsistency desirable? (I guess it will encourage authors to be robust to initialization order, or if they desire a stable order, put their registration script last which has the side-effect of doing depth-first initialization which is pretty nice.)
Comment 2 Dimitri Glazkov 2013-06-25 20:44:55 UTC
I'll just put all of these at the front of the queue. Let's be consistent.
Comment 3 Dimitri Glazkov 2013-06-25 20:47:00 UTC
https://dvcs.w3.org/hg/webcomponents/rev/148112e4f986