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

On Fri, May 22, 2015 at 7:47 AM, Ryosuke Niwa <rniwa@apple.com> wrote:

>
> > 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"?
>

https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Slots-Proposal.md#definitions
>> 'Default slot'


> > 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.
>

Wasn't there talk that declarative before imperative might make imperative
more difficult/impossible?


> - R. Niwa
>
>