W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2015

Re: [webcomponents] How about let's go with slots?

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 21 May 2015 13:09:41 +0900
Message-ID: <CADnb78jr=fKX=jBPPt0MLjgFH0=SeVroe68ECXP8kpOxzeOfUg@mail.gmail.com>
To: Dimitri Glazkov <dglazkov@google.com>
Cc: Scott Miles <sjmiles@google.com>, Ryosuke Niwa <rniwa@apple.com>, "Edward O'Connor" <eoconnor@apple.com>, Travis Leithead <travis.leithead@microsoft.com>, Maciej Stachowiak <mjs@apple.com>, Arron Eicholz <arronei@microsoft.com>, public-webapps <public-webapps@w3.org>
On Tue, May 19, 2015 at 3:18 AM, Dimitri Glazkov <dglazkov@google.com> wrote:
> Given that all vendors agreed that "C" can wait until v2, we could just
> focus on concretizing the "slots" proposal and then put a lid on Shadow DOM
> v1.
>
> What do you think, folks?

This probably works for Mozilla. It would be good to see the proposed
processing model and its implications for an eventual imperative API.
It's somewhat troubling we don't agree on synchronous vs
when-layout-or-event-dispatch-happens.

Also, I suggest we bikeshed the markup in the direction of
slot=some-slot-name and <slot name=some-slot-name> rather than
content-slot=some-slot-name and <content slot=some-slot-name>.


-- 
https://annevankesteren.nl/
Received on Thursday, 21 May 2015 04:10:05 UTC

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