- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Sat, 31 Aug 2024 08:55:04 +0000
- To: public-css-archive@w3.org
> I still think it's somewhat confusing, plus there may be a scenario for an element to both a containing parent and a contained child. > > I'm also not sure about the combo idea, since it also makes sense to have `contain` by itself. We can still allow that, meaning `normal contain` > > Feels like it's either a case of a shorthand or two separate properties stuffed together into one, kind of where it started, right? I wonder if we need this contain keyword at all TBH. This kind of containment can be easily achieved through combinator selectors and perhaps it's better to keep it there rather than create this vt-specific mini-cascade. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10780#issuecomment-2322833462 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 31 August 2024 08:55:05 UTC