- From: Darien Maillet Valentine <notifications@github.com>
- Date: Sat, 02 Apr 2022 13:15:50 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 2 April 2022 20:16:02 UTC
> Is the use case here involve differentiating assigned nodes vs. default content? Or is it about having any content at all? I found ten places where this occurs in our codebase where assigned vs unassigned is the condition. Most of them don’t have default content, but two do. > It would be useful to have a list of concrete use cases for CSS WG folks to study & come up with an appropriate abstraction / name for this feature. I’m working this out backwards a bit, so not a high-level use case, but since there are some very clear patterns here it may still be useful info: Most of these are toggling `hidden` on a containing “grid cell” element (or doing something with the equivalent effect: “this cell doesn’t exist if the slot’s empty”). The more complex remainder could still be roughly summarized as “making a CSS grid respond to assignedness”. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/936#issuecomment-1086715372 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/936/1086715372@github.com>
Received on Saturday, 2 April 2022 20:16:02 UTC