On Wed, Jul 1, 2015 at 3:49 PM, Domenic Denicola <d...@domenic.me> wrote: > From: Anne van Kesteren [mailto:ann...@annevk.nl] >> In a world where custom elements are normal subclassed objects, they would >> just call super() from the constructor to set the browser-supplied bits and >> then add whatever else is needed themselves. > > Yes, that is the Dmitry proposal.
This is confusing. The Element.create callback from Dmitry can also be called post-construction, so it's strictly different from most subclassing scenarios. > Apparently Kevin and Allen's private state proposal is based on private state > being installed at allocation time, so yes, since super() fully allocates the > object, this would prevent private state for custom elements. So are you saying that would make private state harder to use for any kind of subclassing scenario? -- https://annevankesteren.nl/ _______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
