- From: Steve Kobes (Chromium) via GitHub <noreply@w3.org>
- Date: Tue, 18 Nov 2025 19:23:11 +0000
- To: public-css-archive@w3.org
To be clear, `contain: view-transition` is already part of the Scoped View Transitions proposal (see [explainer](https://github.com/WICG/view-transitions/blob/main/scoped-transitions.md#tag-containment) at "Tag containment"). I am strongly opposed to launching Scoped View Transitions without supporting `contain: view-transition`, because that would defeat the goal of enabling composition of encapsulated components. Developers need to be able to choose tags for their participants without worrying about conflicts with ancestor components they don't know about. This issue was about whether to auto-apply `contain: view-transition` to actively transitioning scopes, in case the developer forgets to set it. -- GitHub Notification of comment by skobes-chromium Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12321#issuecomment-3549226635 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 November 2025 19:23:12 UTC