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 27437 - [Custom]: Be clear about whether attached callback should be enqueued when setting prototype
Summary: [Custom]: Be clear about whether attached callback should be enqueued when se...
Status: RESOLVED MOVED
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 treegraph
 
Reported: 2014-11-26 02:11 UTC by William Chen
Modified: 2015-07-06 08:05 UTC (History)
2 users (show)

See Also:


Attachments

Description William Chen 2014-11-26 02:11:26 UTC
http://w3c.github.io/webcomponents/spec/custom/#dfn-created-callback:

"The custom element prototype must be set just prior to invoking callback."

"If the created callback exists for an element, all other callbacks must not be enqueued until after this created callback's invocation had started."

In the steps to set the custom element prototype we have:

http://w3c.github.io/webcomponents/spec/custom/#dfn-set-prototype

3.1. "Enqueue attached callback for ELEMENT"

There is instruction to enqueue an attached callback and instruction to not enqueue the attached callback because it happens before invoking the created callback.
Comment 1 Hayato Ito 2015-07-06 08:05:57 UTC
Moved to https://github.com/w3c/webcomponents/issues/175