RE: Custom element design with ES6 classes and Element constructors from Domenic Denicola on 2015-01-12 (public-webapps@w3.org from January to March 2015)

From: Domenic Denicola <d@domenic.me>
Date: Mon, 12 Jan 2015 17:42:35 +0000
To: Tab Atkins Jr. <jackalmage@gmail.com>, Anne van Kesteren <annevk@annevk.nl>
CC: WebApps WG <public-webapps@w3.org>
Message-ID: <CY1PR0501MB13690AD0D71AC0060971DC43DF430@CY1PR0501MB1369.namprd05.prod.outlook.>

From: Tab Atkins Jr. [mailto:jackalmage@gmail.com] 

> Proto munging isn't even that big of a deal. It's the back-end stuff that's kinda-proto but doesn't munge that's the problem.  This is potentially fixable if we can migrate more elements out into JS space.

It really isn't though, at least, not without a two-stage process like empty constructor() with [[Construct]] semantics that can never be applied to upgraded elements + createdCallback() with [[Call]] semantics that can be applied to upgraded elements after having their __proto__ munged.

Received on Monday, 12 January 2015 17:43:14 UTC