- From: Darien Maillet Valentine <notifications@github.com>
- Date: Sun, 02 Aug 2020 14:18:22 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 2 August 2020 21:18:35 UTC
FWIW, if complex slotted light dom selectors were permitted, I'd expect the selector in the examples above to be `::slotted(.foo .bar)`, not `::slotted(.foo) .bar`. The latter seems to describe a slotted light dom element ".foo" with a descendent shadow element ".bar". Since that scenario can't seemingly occur, the problem might not be obvious ... but switch to just about any other combinator and you get a scenario that _can_ occur (e.g. `::slotted(.foo) + .bar` - "style the shadow `.bar` when preceded by a slot whose assignee matches `.foo`"). AFAIK, selectors like this are _also_ not currently permitted, but I'm unsure if that's a matter of deliberate design or not; they still seem to adhere to query-direct-assignees-only. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/889#issuecomment-667725870
Received on Sunday, 2 August 2020 21:18:35 UTC