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

>> How does it work for redistribution

We've done some investigation and think it can work.

>> and the other downsides that have been brought up?

We have to tackle these deliberately, but mostly we think there is room for
consensus.

>> You're okay with the "required to plaster content-slot='foo' all
over your page" requirement?

Me personally, this is the least palatable part of the `slot` proposal. But
if after all the discussion is over, if the consensus is that the pros
outweigh the cons, then yeah it's not blocking from my perspective. For
sure, I'd at least like a shorter attribute name than `content-slot`, but
seems like that bikeshedding can wait until later. ;)

Scott

On Fri, May 15, 2015 at 5:24 PM, Tab Atkins Jr. <jackalmage@gmail.com>
wrote:

> On Fri, May 15, 2015 at 4:58 PM, Scott Miles <sjmiles@google.com> wrote:
> > Polymer really wants Shadow DOM natively, and we think the `slot`
> proposal
> > can work, so maybe let's avoid blocking on design of an imperative API
> > (which we still should make in the long run).
>
> How does it work for redistribution, and the other downsides that have
> been brought up?  Are you saying that those cases just aren't
> important enough to be blocking at the moment?
>
> You're okay with the "required to plaster content-slot='foo' all over
> your page" requirement?
>
> ~TJ
>