[csswg-drafts] [css-view-transitions-2] Relationship of scoped & nested view transitions, an alternate approach? (#11927)

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

== [css-view-transitions-2] Relationship of scoped & nested view transitions, an alternate approach? ==
Seeing issues like #11926, it seems to me that what people are trying to achieve with nested view transition groups is often better achieved with scoped view transitions, where the whole pseudo tree is part of an element.

It also seems like people struggle with the "layered capture" style issues, of trying to manually copy CSS state from the originating element to the pseudo-element.

What if we can utilize the mechanism for scoped view transitions (in progress) to implement a better version of nesting?

The idea is that instead of creating a nested tree of pseudo elements for the document element, we'll do the following:
- A containing group creates a scope, with its own pseudo-element tree
- The containing group element, together with its generated pseudo-element tree, are captured as content for the document view-transition
- The pseudo element tree for the scope is not a view-transition per-se, as it doesn't have its own promises and its lifecycle is tied to the parent view transition.

This has the potential to fix a lot of the issues with nesting. Instead of copying state from the element to the pseudo-element, the element can generate content that has all of this state and can include sub-element that participate in the view transition by themselves.

Thoughts?

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


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

Received on Wednesday, 12 March 2025 18:11:59 UTC