On Fri, May 15, 2015 at 4:58 PM, Scott Miles <sjmi...@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?


Reply via email to