Re: Proposal for changes to manage Shadow DOM content distribution

On Wed, Apr 22, 2015 at 2:29 PM, Ryosuke Niwa <rniwa@apple.com> wrote:
>> On Apr 22, 2015, at 8:52 AM, Domenic Denicola <d@domenic.me> wrote:
>> Between content-slot-specified slots, attribute-specified slots, element-named slots, and everything-else-slots, we're now in a weird place where we've reinvented a micro-language with some, but not all, of the power of CSS selectors. Is adding a new micro-language to the web platform worth helping implementers avoid the complexity of implementing CSS selector matching in this context?
>
> I don't think mapping an attribute value to a slot is achievable with a content element with select attribute.

<content select="[my-attr='the slot value']">

> I don't think defining a slot based on an attribute value is something we'd like to support.

That is *literally* what your proposal already is, except limited to
only paying attention to the value of the "content-slot" attribute.

~TJ

Received on Wednesday, 22 April 2015 21:39:29 UTC