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

Re: ES6 and upgrading custom elements

From: Dimitri Glazkov <dglazkov@google.com>
Date: Tue, 6 Jan 2015 09:13:56 -0800
Message-ID: <CADh5Ky2hYuJoXQvy_JWjx25EEkY8D9v8qWg9VUxXZAnms-aduQ@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: WebApps WG <public-webapps@w3.org>
That section needs to be updated, because the ES6 spec had shifted a little
bit with regard to @@create. Filed
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27769.

Conceptually, when I wrote it I'd imagined that the constructor will be
called only when you explicitly invoke it (new FooElement...). When parsing
or upgrading, the constructor would not be called. The createdCallback will
be invoked in either case.

:DG<


On Tue, Jan 6, 2015 at 7:21 AM, Anne van Kesteren <annevk@annevk.nl> wrote:

> It's not clear to me from
> https://w3c.github.io/webcomponents/spec/custom/#es6 how the upgrade
> works. From the pre-ES6 setup you can work out through inference that
> upgrading is supposed to mutate the prototype of the element in
> question.
>
> But it seems that mutating the prototype is not sufficient for ES6. We
> want an element created through the constructor, no? (Let's leave
> aside the question for now as to how this subclassing would work,
> that's already discussed elsewhere.)
>
>
> --
> https://annevankesteren.nl/
>
>
Received on Tuesday, 6 January 2015 17:14:23 UTC

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