- From: hober <notifications@github.com>
- Date: Mon, 06 Apr 2020 10:11:47 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 6 April 2020 17:12:00 UTC
Overall I think this looks great. One minor concern I have is with the exclusivity of the slot assignment modes, though I think my concern could easily be addressed by some syntactic sugar. It's common to have special behavior with one child (or a few children) and some kind of default behavior for the rest. Consider the following markup: ```html <details> <summary>This is the summary.</summary> and <p>these <p>are <p>the <p>details </details> ``` The proposed imperative API lets you easily handle `<summary>`. It would be nice if it were easy/straightforward to implement a default slot using the imperative API, so that the rest of `<details>`'s children could be taken care of easily. Maybe something like `shadowRoot.setDefaultSlot(slot)`. You do some manual slotting and then everything not slotted ends up in the default slot. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/486#issuecomment-609922109
Received on Monday, 6 April 2020 17:12:00 UTC