- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Jan 2023 10:00:17 +0000
- To: public-css-archive@w3.org
> Both can be done with the proposal above to use `isolation: isolate` for these elements. This won't literally use `isolation: isolate` in any observable way. It will just create a [stacking context](https://drafts.csswg.org/css2/#stacking-context) in the same way [`opacity`](https://w3c.github.io/csswg-drafts/css-color/#transparency) does for values less than `1` (and yes, in the same way `isolation: isolate` does). > But with respect to whether the shared element needs to be a containing block, there's good points for both options: I like features that have a default that prevents common errors, especially if that error isn't immediately obvious. But in this case any error will be immediately obvious. And, I think there will be cases where the developer really doesn't want a containing block here. -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8139#issuecomment-1386784613 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 January 2023 10:00:18 UTC