18747 2012-08-30 21:28:49 +0000 [Custom]: Specify invoking "readyCallback" 2013-04-22 21:59:01 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED FIXED P2 normal --- 18720 1 dglazkov dglazkov morrita sjmiles sorvell public-webapps-bugzilla oldest_to_newest 73088 0 dglazkov 2012-08-30 21:28:49 +0000 The "created" callback is invoked _after_ we traversed through CHAIN. This is the callback to use to do stuff your particular element instance. 73091 1 dglazkov 2012-08-30 21:32:25 +0000 *** Bug 18731 has been marked as a duplicate of this bug. *** 73092 2 dglazkov 2012-08-30 21:34:29 +0000 One concern raised: the "created" callback effectively acts as a constructor, and this mechanism alone does not provide a way to invoke the "created" callback of the super-class. 73093 3 dglazkov 2012-08-30 21:43:15 +0000 One idea: pass the prototype's super created method: created: function(superCreated) { } 77458 4 dglazkov 2012-10-30 21:58:19 +0000 http://dvcs.w3.org/hg/webcomponents/rev/cad29a7d9a11 80050 5 sjmiles 2012-12-12 23:10:42 +0000 For the work my team is doing, 'create' is a critical entry-point (initialization after all shadow roots are created), but it turns out we also could use an entry-point *before* the shadow roots are created. A strawman API: // called on the ultimate subclass // when the element in instantiated // but BEFORE any shadowRootCreated. // inSuper argument provided to call inherited 'created' // which is otherwise private created: function(inSuper) // called on each extendor, from oldest to youngest, // when it's respective shadow root is intantiated // inRoot argument provides reference to the shadow root // which MAY otherwise be private shadowRootCreated: function(inRoot) // called on the ultimate subclass // when the element in instantiated // and AFTER all shadowRootCreated. // inSuper argument provided to call inherited 'created' // which is otherwise private ready: function(inSuper) Unfortunately increases complexity, but I suggest we need to service these custom inheritance trees properly. 80051 6 sjmiles 2012-12-12 23:12:02 +0000 The comment above overlaps with this bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=18748. Maybe I should have made a new bug altogether? 85873 7 dglazkov 2013-04-10 20:13:48 +0000 *** Bug 21408 has been marked as a duplicate of this bug. *** 85875 8 dglazkov 2013-04-10 20:14:08 +0000 *** Bug 21409 has been marked as a duplicate of this bug. *** 85906 9 dglazkov 2013-04-10 22:28:15 +0000 https://dvcs.w3.org/hg/webcomponents/rev/50480689d0bf 86495 10 dglazkov 2013-04-22 21:59:01 +0000 https://dvcs.w3.org/hg/webcomponents/rev/d0d9310e750a https://dvcs.w3.org/hg/webcomponents/rev/0854a1983551 https://dvcs.w3.org/hg/webcomponents/rev/b37a366e3682 I think this is done now. Please look over the spec and make sure I didn't booger it up too much.