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

Re: Custom elements ES6/ES5 syntax compromise, was: document.register and ES6

From: Dimitri Glazkov <dglazkov@google.com>
Date: Wed, 20 Feb 2013 10:02:06 -0800
Message-ID: <CADh5Ky1r6f4eM8roQWtZVfUaGM6XcjBOu=y3X9Xmv37jstYN4g@mail.gmail.com>
To: Scott Miles <sjmiles@google.com>
Cc: Daniel Buchner <daniel@mozilla.com>, Anne van Kesteren <annevk@annevk.nl>, Boris Zbarsky <bzbarsky@mit.edu>, Erik Arvidsson <arv@chromium.org>, public-webapps <public-webapps@w3.org>
On Wed, Feb 20, 2013 at 9:58 AM, Scott Miles <sjmiles@google.com> wrote:
> Since many of these cases are 'semantic' elements, whose only raison d'Ítre
> (afaik) is having a particular localName, I'm not sure how we get around
> this without being able to specify an 'extends' option.
> document.register('fancy-header', {
>   prototype: FancyHeaderPrototype,
>   extends: 'header'
> ...

Can you help me understand why we need to do this? Since there is no
HTMLHeaderPrototype, we will never have an issue with forming the
wrong prototype chain. So <header is="fancy-header"> should work just
as well as <section is="fancy-header">, and so would <fancy-header>.

Received on Wednesday, 20 February 2013 18:02:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:58 UTC