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 25142 - [Custom]: Missing created callback should not prevent other callbacks from being enqueued.
Summary: [Custom]: Missing created callback should not prevent other callbacks from be...
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL: http://w3c.github.io/webcomponents/sp...
Whiteboard:
Keywords:
Depends on:
Blocks: 14968
  Show dependency tree / graph
 
Reported: 2014-03-24 19:22 UTC by William Chen
Modified: 2014-05-12 22:35 UTC (History)
4 users (show)

See Also:

Attachments

Description William Chen 2014-03-24 19:22:01 UTC 
In the description of the created callback the spec currently says:

"All other callbacks must not be enqueued until after the created callback's invocation had started."

It's not very clear what should happen when there is no created callback transferred from the prototype. The way it's currently worded, there is no callback to invoke and no other callbacks would be enqueued. This seems like the wrong behavior to me.
Comment 1 Dominic Cooney 2014-03-25 07:20:13 UTC 
IIRC in Blink if there is no created callback we swizzle the wrapper's prototype (if any) and change the applicability of :unresolved at that point, then enqueue callbacks as if the created callback has run.

So I agree with the direction of this bug report.
Comment 2 Dimitri Glazkov 2014-05-05 17:59:07 UTC 
Good point. Working on a better wording...
Comment 3 Dimitri Glazkov 2014-05-05 18:35:05 UTC 
WDYT? https://github.com/w3c/webcomponents/pull/9