Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)

So here are two concrete use cases I'd like to solve:

- details/summary, i.e. a way to select summary:first-of-type
- select/option or similar list-like constructs, e.g. [this list markup](https://gist.github.com/domenic/3fcd954f54dd33620cd822c6b776d0df). Here you want to put every child (or perhaps every child with a given tag name?) into a container in the shadow DOM, without requiring that users add `slot="slot1"`, `slot="slot2"`, `slot="slot3"`, ... to all the children.

I am curious about the internal mechanisms Blink and WebKit use for their UA shadow roots, and whether we could clean those up into a proposal for something to expose to the web platform.

-- 
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/726#issuecomment-367370195

Received on Wednesday, 21 February 2018 15:48:52 UTC