Re: [webcomponents]: Of weird script elements and Benadryl from Allen Wirfs-Brock on 2013-04-14 (public-webapps@w3.org from April to June 2013)

From: Allen Wirfs-Brock <allen@wirfs-brock.com>
Date: Sun, 14 Apr 2013 12:07:19 -0700
To: Scott Miles <sjmiles@google.com>
Cc: Daniel Buchner <daniel@mozilla.com>, Rick Waldron <waldron.rick@gmail.com>, John J Barton <johnjbarton@johnjbarton.com>, Dimitri Glazkov <dglazkov@google.com>, Rafael Weinstein <rafaelw@google.com>, public-webapps <public-webapps@w3.org>, Blake Kaplan <mrbkap@mozilla.com>, William Chen <wchen@mozilla.com>, Jonas Sicking <jonas@sicking.cc>, Steve Orvell <sorvell@google.com>, Dave Herman <dherman@mozilla.com>, Boris Zbarsky <bzbarsky@mit.edu>
Message-Id: <E90F262D-C505-4493-B948-460C87192530@wirfs-brock.com>

On Apr 14, 2013, at 11:40 AM, Scott Miles wrote:

> >> Here are four ways to avoid the subclassing problem for custom elements
> >> 1)  Only allow instances of custome dom elements to be instantiated using document.createElement("x-foo"). 
> 
> Wearing web developer hat, I never make elements any other way than createElement (or HTML), so this would be standard operating procedure, so that's all good if we can get buy in.

However, I believe that some people such as Alex Russell have been advocating that WebIDL should be allow constructor-like interfaces  to support expressions such as:
       new HTMLWhateverElement()

It would be future hostile to make that impossible, but support could reasonably wait for ES6 support.

> 
> >> 2, 3, 4
> 
> I believe have been suggested in one form or another, but as I mentioned, were determined to be non-starters for Gecko. I don't think we've heard anything from IE team.

Well #4 has been accepted for ES6 by all TC39 participants including Mozilla and Microsoft and is going to happen.  The basic scheme was actually suggested a member of the SpiderMonkey team so I'm sure we'll get it worked out for Gecko. 

Allen

Received on Sunday, 14 April 2013 19:07:55 UTC