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 22566 - [Custom]: Element upgrade algorithm set prototype right before createdCallback is called
Summary: [Custom]: Element upgrade algorithm set prototype right before createdCallbac...
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-07-03 22:37 UTC by Dimitri Glazkov
Modified: 2013-08-07 21:46 UTC (History)
1 user (show)

See Also:

Attachments

Description Dimitri Glazkov 2013-07-03 22:37:16 UTC 
If we do, then there will never be a problem of accessing methods/properties of an object whose createdCallback hasn't been called yet.
Comment 1 Dimitri Glazkov 2013-07-03 22:38:52 UTC 
This also means that the element remains unresolved even though it is no longer in the unresolved candidate pool. We should make sure the :unresolved still applies until the prototype is set.
Comment 2 Dominic Cooney 2013-07-04 02:27:40 UTC 
I think this is a good idea; I have experimentally implemented this in Blink to get feedback from web developers.
Comment 3 Dimitri Glazkov 2013-08-07 21:31:08 UTC 
https://dvcs.w3.org/hg/webcomponents/rev/18526224760f
Comment 4 Dimitri Glazkov 2013-08-07 21:46:06 UTC 
https://dvcs.w3.org/hg/webcomponents/rev/77d599e27f37