- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Jan 2024 17:14:30 +0000
- To: public-css-archive@w3.org
For a strawman proposal, I suggest we break style containment into two parts: 1. Contain named items (e.g. scroll-timeline-name, view-timeline-name, anything else, maybe counters?) 2. Everything else? Maybe someone who's more knowledgeable about what restrictions container queries need could comment which parts of style containment are needed here. Maybe those not needed could be grouped into bucket 1. Assuming this split, [container-type](https://drafts.csswg.org/css-contain-3/#container-type) would only apply the second part, allowing named items to leak out, while content-visibility would apply both since we avoid needing to compute style for any of the descendents. Then, we have to decide on the behavior of the contain property: 1. Does `contain: style` means both parts? I'd lead towards yes, but could see going both ways. 2. Do we expose keywords for the finer grained parts? If so, which ones? -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8915#issuecomment-1883461265 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 9 January 2024 17:14:32 UTC