[csswg-drafts] [css-view-transitions-2] [scoped] Should the scope be self-participating by default? (#12320)

skobes-chromium has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-view-transitions-2] [scoped] Should the scope be self-participating by default? ==
This issue tracks an open question about the behavior of [Scoped View Transitions](https://github.com/WICG/view-transitions/blob/main/scoped-transitions.md). Further context appears in the document [Self-Participating Scopes](https://bit.ly/svt-sps).

**Q: Should the scope be self-participating by default?**

If we allow self-participating scopes (#12319) then we should consider giving the scope a default value for `view-transition-name` during the transition. (This would apply **only** during the transition, since we can't predict that an element will be a scope until the developer invokes `startViewTransition` on it.)

We could reuse `root` for this, or introduce a new predefined name.

This would make every scope self-participating unless the developer overrides it by setting `view-transition-name: none` on the scope.  That's similar to how document-level view transitions currently work.

Chromium 139 doesn't currently do this, and will treat scopes as `view-transition-name: none` by default.

My recommendation is to make scopes self-participating by default, unless we decide not to allow self-participation.

cc @noamr @vmpstr @flackr @bramus @jakearchibald 


Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12320 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 11 June 2025 19:31:48 UTC