- From: Ryosuke Niwa <rniwa@apple.com>
- Date: Wed, 22 Apr 2015 14:29:06 -0700
- To: Domenic Denicola <d@domenic.me>
- Cc: Brian Kardell <bkardell@gmail.com>, "Edward O&,#39 Connor" <eoconnor@apple.com>, Jan Miksovsky <jan@component.kitchen>, WebApps WG <public-webapps@w3.org>
> 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
Received on Wednesday, 22 April 2015 21:29:37 UTC