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

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

From: Ryosuke Niwa <rniwa@apple.com>
Date: Thu, 21 May 2015 23:47:20 -0700
Cc: Dimitri Glazkov <dglazkov@google.com>, Travis Leithead <travis.leithead@microsoft.com>, Anne van Kesteren <annevk@annevk.nl>, Scott Miles <sjmiles@google.com>, Edward O'Connor <eoconnor@apple.com>, Maciej Stachowiak <mjs@apple.com>, Arron Eicholz <arronei@microsoft.com>, public-webapps <public-webapps@w3.org>
Message-id: <1F52EED5-F722-4C8D-A612-05AF3EABAB21@apple.com>
To: Wilson Page <wilsonpage@me.com>

> On May 21, 2015, at 11:33 PM, Wilson Page <wilsonpage@me.com> wrote:
> 
> From experience building components for Firefox OS I think the 'default slot' pattern will fulfill most of our use-cases. This means we won't have to burden our component users by requiring them to add `slot="foo"` all over the place.

Could you clarify what you're referring to by "'default slot' pattern"?

> Is it fair to say that if this declarative API lands in V1, it's unlikely we'll see imperative API in V2? Have we not exhausted all the options?

At F2F, basically all browser vendors have agreed that we eventually want the imperative API, and we (Apple) are certainly interested in the imperative API being included in v2.

- R. Niwa
Received on Friday, 22 May 2015 06:47:51 UTC

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