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

Re: ES6 and upgrading custom elements

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 6 Jan 2015 18:56:57 +0100
Message-ID: <CADnb78iLe1rJN=FqsWNCO8WxHfBWqCH9a_HsgDHywaC+63jwig@mail.gmail.com>
To: Dimitri Glazkov <dglazkov@google.com>
Cc: WebApps WG <public-webapps@w3.org>
On Tue, Jan 6, 2015 at 6:13 PM, Dimitri Glazkov <dglazkov@google.com> wrote:
> 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.

Yeah, there's issues in general there, such as ES6 giving up on
explaining all of DOM :-(

> 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.

Would you do the prototype munging that is specified in
"createdCallback" today? (I think it would be more clear if we made
that prototype munging part of the upgrade algorithm by the way.) How
else would that work? Pass a reference to the old element and let the
developer handle it?

Received on Tuesday, 6 January 2015 17:57:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:43 UTC