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

> > Seeing issues like [#11926](https://github.com/w3c/csswg-drafts/issues/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 
> > What if we can utilize the mechanism for scoped view transitions (in progress) to implement a better version of nesting?
> > […]
> 
> I’m not entirely following here. Do you have an example of what the DOM + CSS + resulting pseudo tree would look like?

Sure! It would look just like in scoped view transitions. That's not finalized yet, but something like:

```
html
  ::view-transition
    ::view-transition-group(root)
    ::view-transition-group(my-list)
      ::view-transition-image-pair(my-list)
         ::view-transition-old(my-list)
         ::view-transition-new(my-list)

/* the output of this, including the ::view-transition pseudo as it's animating, 
feeds into ::view-transition-new(my-list) */
my-list 
  ::view-transition
    ::view-transition-group(list-item-1)
    ...
```

The list items are grouped into the scope of my-list, and the final product of the my-list view transition is rendered into `::view-transition-new(my-list)`.

The borders, clipping, etc. on `my-list` are rendered as usual when creating the render output of my-list, and can clip the `::view-transition` pseudo.

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


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

Received on Friday, 21 March 2025 16:31:25 UTC