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

Re: document.register and ES6

From: Scott Miles <sjmiles@google.com>
Date: Fri, 8 Feb 2013 09:49:49 -0800
Message-ID: <CAHbmOLYyDXf62dn4u92mokJia3W7wqK7pZSesVGUBgWGHBqjVw@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: Erik Arvidsson <arv@chromium.org>, public-webapps <public-webapps@w3.org>, daniel <daniel@mozilla.com>, Dimitri Glazkov <dglazkov@google.com>
On Fri, Feb 8, 2013 at 9:25 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

> On 2/8/13 5:11 PM, Erik Arvidsson wrote:
>
>> 1. We cannot really extends anything else but HTMLElement/**
>> HTMLUnknownElement.
>>
>
> Note that this restriction is not limited to polyfills.  Extending other
> HTMLElements with a custom tagname seems ... highly undesirable to me. In
> particular, if you have an element whose localName is not "button" but
> which is an HTMLButtonElement then some aspects of its buttonness will work
> in some UAs and other will not, and the set will depend on the UA and on
> the extensions installed and so forth.
>
> If we need to subclass built-in non-generic HTML elements we need to do so
> with nodes which have the right localName.
>
>
In our recent debates, the general agreement is that we would support this
syntax:

<button is="my-button">

Doesn't that allow us to have proper localName?



> -Boris
>
Received on Friday, 8 February 2013 17:50:17 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:57 GMT