W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

RE: ES6 and upgrading custom elements

From: Domenic Denicola <d@domenic.me>
Date: Wed, 7 Jan 2015 12:26:45 +0000
To: Anne van Kesteren <annevk@annevk.nl>
CC: Dimitri Glazkov <dglazkov@google.com>, WebApps WG <public-webapps@w3.org>
Message-ID: <CY1PR0501MB13698C2E4317FE94D73714CDDF460@CY1PR0501MB1369.namprd05.prod.outlook.com>
From: annevankesteren@gmail.com [mailto:annevankesteren@gmail.com] On Behalf Of Anne van Kesteren

> That's why I tried to scope this thread to upgrading and not the script side.
>
> The main question is how you tie MyInputElement to something like <my-input> and have that actually work. It seems Dimitri's answer is that you don't, you use <input is=my-input> in combination with a (delayed) prototype mutation and creation callback. And you use createElement("input", "my-input") or the constructor on the script side of things.

Oh my goodness, I'm sorry. I completely misunderstood what was meant by "upgrading." My fault entirely, as it's a well-defined custom elements term.

I see the problem now. I'll try to think on it harder and get back to you. In the meantime, apologies for derailing the thread.

Received on Wednesday, 7 January 2015 12:27:15 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:25 UTC