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

Re: Minimum viable custom elements

From: Anne van Kesteren <annevk@annevk.nl>
Date: Fri, 16 Jan 2015 18:58:53 +0100
Message-ID: <CADnb78hxaqH-V3Hwkeam+r0aekryke-PWwAyc8isRkaM_K66yA@mail.gmail.com>
To: Ryosuke Niwa <rniwa@apple.com>
Cc: Domenic Denicola <d@domenic.me>, Dimitri Glazkov <dglazkov@google.com>, Erik Arvidsson <arv@google.com>, Boris Zbarsky <bzbarsky@mit.edu>, public-webapps <public-webapps@w3.org>
On Fri, Jan 16, 2015 at 2:29 AM, Ryosuke Niwa <rniwa@apple.com> wrote:
> And I'm suggesting to do the same (picking the simplest design) in HTML custom elements by only supporting synchronous definition of elements, and letting authors and frameworks decide how to "upgrade" existing elements if they want to.

That seems to put us at an impasse. I get the impression this scenario
is important to Google and their two-stage constructor design
addresses it. To convince them it sounds like they need to see at
least a plausible strategy for custom elements v2 that addresses this.
At which point we're back to something like "dummy replacement" with
its problems. Or perhaps something like "HTML modules", where you
import a whole swath of (custom) elements at once.


-- 
https://annevankesteren.nl/
Received on Friday, 16 January 2015 17:59:17 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:25 UTC