W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2013

Re: [webcomponents]: Platonic form of custom elements declarative syntax

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Thu, 11 Apr 2013 12:32:47 -0400
Message-ID: <5166E5AF.9080107@mit.edu>
To: public-webapps@w3.org, "public-script-coord@w3.org" <public-script-coord@w3.org>
On 4/11/13 12:23 PM, Allen Wirfs-Brock wrote:
> So why don't you make "register" a static method on HTMLElement and then
> define the <element> semantics so it automatically does:
>      MyElement.register()
>
> This would normally invoke the inherited static method

I lost track of something here.  Why would it do that?  Does MyElement 
have Element on its proto chain?  MyElement.prototype certainly has 
Element.prototype on _its_ proto chain, but that's a separate concern 
from what happens with the interface objects...  Is this something that 
ES6 classes define differently from current WebIDL and implementations, 
and if so, do we need to align the two somehow?

-Boris
Received on Thursday, 11 April 2013 16:33:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:48 UTC