- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 May 2021 17:47:33 +0000
- To: public-css-archive@w3.org
So it turns out [content-visibility](https://drafts.csswg.org/css-contain-2/#content-visibility) already has the behavior of "turning on" various types of containment behavior from outside the `contain` property. It doesn't change the computed value of `contain`, only the [used/applied value](https://github.com/w3c/csswg-drafts/issues/5913#issuecomment-836692271) – so it's not really one property setting the other, but two properties that can trigger similar behavior. We also do this with things like `block formatting context` - which can now be set explicitly with contain, but is also required & applied by other properties. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6174#issuecomment-844329948 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 May 2021 17:47:46 UTC