- From: Bramus via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Mar 2025 13:28:07 +0000
- To: public-css-archive@w3.org
> Seeing issues like 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 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. FWIW: This was only needed it the manual workaround _(the box with the hotpink border in [the playground](https://codepen.io/bramus/full/EaxvMXG/11b9fcbe8ebf42034110d3b486db037f))_, which was used to show what the problem is. The solution with the suggested wrapper for nested pseudos _(the box underneath the hotpink one)_ requires no style duplication. The one thing that is required though, is to add a `border-radius` to the `::view-transition-group-content(albums-wrapper)`, but only if one was used on the original element outer element. This is necessary to make the clipping happen correctly. AFAICT that is the only style that needs to be applied onto the proposed `::view-transition-group-content(albums-wrapper)`. > 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? -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11927#issuecomment-2743367351 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 13:28:08 UTC