W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2015

Re: Proposal for changes to manage Shadow DOM content distribution

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 22 Apr 2015 14:38:41 -0700
Message-ID: <CAAWBYDCyUbtX9gROPam1bqdsvohnzt67HgLpYDmv=6s1RHCs7Q@mail.gmail.com>
To: Ryosuke Niwa <rniwa@apple.com>
Cc: Domenic Denicola <d@domenic.me>, Brian Kardell <bkardell@gmail.com>, "Edward O&amp,#39 Connor" <eoconnor@apple.com>, Jan Miksovsky <jan@component.kitchen>, WebApps WG <public-webapps@w3.org>
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

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:31 UTC