Re: [webcomponents] How about let's go with slots? from Justin Fagnani on 2015-05-18 (public-webapps@w3.org from April to June 2015)

From: Justin Fagnani <justinfagnani@google.com>
Date: Mon, 18 May 2015 16:20:34 -0700
To: Domenic Denicola <d@domenic.me>
Cc: Daniel Freedman <dfreedm@google.com>, Dimitri Glazkov <dglazkov@google.com>, Scott Miles <sjmiles@google.com>, Ryosuke Niwa <rniwa@apple.com>, "Edward O'Connor" <eoconnor@apple.com>, Anne van Kesteren <annevk@annevk.nl>, Travis Leithead <travis.leithead@microsoft.com>, Maciej Stachowiak <mjs@apple.com>, Arron Eicholz <arronei@microsoft.com>, Alex Russell <slightlyoff@google.com>, public-webapps <public-webapps@w3.org>
Message-ID: <CAEKsHmAvoX6NF1vgqqW4SZHHSwYhDvhPLoiJ6mCYxFr57aUNAA@mail.gmail.com>

Like we pointed out in the previous thread, adding enough special cases to
slots leads to select.

At this point we're much more interested in agreeing on something rather
than nothing.

On Mon, May 18, 2015 at 3:58 PM, Domenic Denicola <d@domenic.me> wrote:

> I was thinking opposed. I don’t see any reason to invent two ways to do
> the same thing.
>
> If we do support content-slot then I think we should allow <details><div
> content-slot="summary">...</div>...</details> and a few others.
>
>

Received on Monday, 18 May 2015 23:21:22 UTC