22455 2013-06-25 14:58:19 +0000 [Custom]: Consider inserting unresolved elements at the start of the map. 2013-06-25 20:47:00 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC Linux RESOLVED FIXED P2 normal --- 14968 1 dominicc dglazkov public-webapps-bugzilla oldest_to_newest 89817 0 dominicc 2013-06-25 14:58:19 +0000 "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.) 89829 1 dglazkov 2013-06-25 18:03:10 +0000 for reference, test here: https://codereview.chromium.org/17707002/diff/1/LayoutTests/fast/dom/custom/callbacks-upgrade.html 89847 2 dglazkov 2013-06-25 20:44:55 +0000 I'll just put all of these at the front of the queue. Let's be consistent. 89848 3 dglazkov 2013-06-25 20:47:00 +0000 https://dvcs.w3.org/hg/webcomponents/rev/148112e4f986