Re: [csswg-drafts] [css-view-transitions-2] [scoped] Clarify the ::v-t box and stacking context position relative to the scope (#12324)

I also favor option 1.  My primary concern is that it should be possible, inside the scope, to mix participating elements with interactive non-participating elements, an effect that developers currently achieve with document transitions by writing `html { view-transition-name: none } ::view-transition { pointer-events: none }`.

Option 2 makes this effect impossible.  The developer then has to restructure their DOM so that the interactive elements are outside of the scope, which may be very constraining and is at odds with the principle that view transitions are independent of DOM structure.  Option 2 pushes people away from using scoped view transitions, since the answer to "Q: How do I mix interactive and transitioning elements?" will be "A: Sorry this can't really be done with scoped, you have to keep using `document.startViewTransition()`..."  So I don't think it is inconsequential.

I am happy with the `-ua-root` tag, or something not developer-exposed, for the non-participating scope's `::v-t-group`.

-- 
GitHub Notification of comment by skobes-chromium
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12324#issuecomment-3642117111 using your GitHub account


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

Received on Thursday, 11 December 2025 14:11:42 UTC