- From: Steve Kobes (Chromium) via GitHub <noreply@w3.org>
- Date: Thu, 12 Mar 2026 13:47:04 +0000
- To: public-css-archive@w3.org
skobes-chromium has just created a new issue for https://github.com/w3c/csswg-drafts:
== [css-view-transitions-2] [scoped] Force tag containment for active transitions ==
On #13123 it was resolved to add the UA stylesheet rule `:active-view-transition { view-transition-scope: all }`, presumably with the intention of achieving the behavior described in the [explainer](https://github.com/WICG/view-transitions/blob/main/scoped-transitions.md#tag-containment) as follows:
"If the scope does not have `view-transition-scope: all`, it acquires the behavior of `view-transition-scope: all` while the transition is running."
However, the proposed UA stylesheet rule would still allow the developer to override the behavior by setting `view-transition-scope: none` explicitly. We should decide between the following options:
1. Allow the developer to override the behavior.
2. Add `!important` to the UA stylesheet rule.
3. Specify the behavior without relying on the UA stylesheet.
I think Option 3 is closest to what Chrome is doing today since we implemented this in StyleAdjuster.
@vmpstr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13637 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 12 March 2026 13:47:05 UTC