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: Daniel Buchner <daniel@mozilla.com>
Date: Thu, 14 Feb 2013 17:32:30 -0800
Message-ID: <CAHZ6zJGzzMMhwJjFdAP=BkRMfaqG2soq4QysMVZu5NrU4PoqXw@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: Anne van Kesteren <annevk@annevk.nl>, Rick Waldron <waldron.rick@gmail.com>, public-webapps <public-webapps@w3.org>, Erik Arvidsson <arv@chromium.org>, Scott Miles <sjmiles@google.com>, Dimitri Glazkov <dglazkov@google.com>
What does it actually profit us to singularly tie document.register to
require an ES6-esque syntax before it lands anyway? No one is saying not to
use it *when it arrives*, we're offering a way to make sure the polyfill
layer isn't needlessly bound to inconsequential externalities.

Hell, if you wanted a single API, call the property "descriptor" (or
something else that's general) and have it take both by checking what kind
of object the value is... ***ducks***
On Feb 14, 2013 5:14 PM, "Boris Zbarsky" <bzbarsky@mit.edu> wrote:

> On 2/14/13 6:03 PM, Dimitri Glazkov wrote:
>> Since these are two separate steps, I technically don't _need_ to put
>> HTMLButtonElement.call(this) into my element's constructor -- it's a
>> sure bet it will just be a useless dummy.
> For HTMLButtonElement, perhaps.  But for HTMLImageElement that's less
> clear.
> -Boris
Received on Friday, 15 February 2013 01:34:28 UTC

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