- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 03 Jan 2023 16:07:38 +0000
- To: public-css-archive@w3.org
+1 from me as well to remove the contain requirement. But one side effect of contain: layout (or paint) is that the element becomes a stacking context. And we do need this to capture the element as an atomic image. The spec could say that if an element has a non-none computed value for `view-transition-name` then it becomes a stacking context but I want to avoid unexpected side-effects from applying this property. Especially if a developer adds this property only for the duration of the transition and the layout changes in unexpected ways. So could we require that developers explicitly ensure that named elements create a stacking context? It could be from an effect (like `opacity`) or by adding `isolation: isolate` to the element. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8139#issuecomment-1369947409 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 3 January 2023 16:07:40 UTC