> 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. - R. Niwa