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 23778 - [Custom]: Avoid difference in "created" callback ordering in parsing vs. cloning
Summary: [Custom]: Avoid difference in "created" callback ordering in parsing vs. cloning
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 14968
  Show dependency tree / graph
 
Reported: 2013-11-08 21:49 UTC by Dimitri Glazkov
Modified: 2013-11-19 17:50 UTC (History)
2 users (show)

See Also:

Attachments

Description Dimitri Glazkov 2013-11-08 21:49:15 UTC 
First discussed in: https://groups.google.com/d/topic/polymer-dev/a4rFb6NgktE/discussion

As specified now, the order of "created" callback in a DOM tree will be different for for parsing versus cloning

For example, in http://jsbin.com/uxIbOQo/2/edit?js,console
The output is:

"order of callbacks when parsing:"
"C"
"B"
"A"
"order of callbacks when cloning:"
"A"
"B"
"C"

This seems inconsistent. We should consider removing the special-casing of callback ordering in HTML parser.
Comment 1 Dominic Cooney 2013-11-19 03:46:26 UTC 
Implementer feedback: I have made Blink follow this proposed ordering.