Re: [csswg-drafts] [css-view-transitions-2] [scoped] Should the scope have contain:v-t by default? (#12321)

> There are two options:
> 
> 1. We introduce `contain: view-transition` similar to `contain: names` that [@flackr](https://github.com/flackr) proposed in [[scroll-animations-1] blocking effects of timeline-scope #8915 (comment)](https://github.com/w3c/csswg-drafts/issues/8915#issuecomment-1883461265) and say that we apply this property for the duration of the scoped transition
> 2. We roughly do the same thing as 1 but without introducing a new property (ie implementation magic)
> 
> We propose adding something like `contain: view-transition / names` and using it (option 1). Another reason for this is that the developer should be able to structure their code with components that don't expose their names

I support adding an explicit `contain: view-transition-name` as it allows avoiding conflicts *before* the transition starts.
We can then express (1) as a UA stylesheet:
```css
:active-view-transition {
  contain: view-transition;
}
```

I wonder though if this containment conflicts with other forms of containment and should be a separate property?

-- 
GitHub Notification of comment by noamr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12321#issuecomment-3549152814 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:05:11 UTC