> On Apr 21, 2015, at 10:23 PM, Justin Fagnani <justinfagn...@google.com> wrote: > > I do want the ability to redirect distributed nodes into a holes in the base > template, so that part is welcome to me. However, my first reaction to the > slot idea is that forcing users to add the content-slot attribute on children > significantly impairs the DOM API surface area of custom elements. > > For the single-level distribution case, how is this different from <content > select="[content-slot=name]"> except that content select can distribute based > on features of the children that might already exist, like tag names or an > attribute?
At the conceptual level, they're equivalent. However, we didn't find the extra flexibility of using CSS selectors compelling as we mentioned in our proposal [1]. [1] See points 3 and 4 in https://github.com/w3c/webcomponents/wiki/Proposal-for-changes-to-manage-Shadow-DOM-content-distribution#some-issues-with-the-current-shadow-dom-spec - R. Niwa
