25142 2014-03-24 19:22:01 +0000 [Custom]: Missing created callback should not prevent other callbacks from being enqueued. 2014-05-12 22:35:49 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified All All RESOLVED FIXED http://w3c.github.io/webcomponents/spec/custom/#types-of-callbacks P2 normal --- 14968 1 wchen dglazkov annevk dominicc mike public-webapps public-webapps-bugzilla oldest_to_newest 102850 0 wchen 2014-03-24 19:22:01 +0000 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. 102869 1 dominicc 2014-03-25 07:20:13 +0000 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. 105061 2 dglazkov 2014-05-05 17:59:07 +0000 Good point. Working on a better wording... 105063 3 dglazkov 2014-05-05 18:35:05 +0000 WDYT? https://github.com/w3c/webcomponents/pull/9 105779 4 dglazkov 2014-05-12 22:35:49 +0000 https://github.com/w3c/webcomponents/commit/61093a7d9562a6ea5a1926529406cf1bc3255778