- From: Callie Riggins Zetino via GitHub <sysbot+gh@w3.org>
- Date: Fri, 17 May 2024 19:05:57 +0000
- To: public-css-archive@w3.org
Our use case typically would benefit most from Option 1. We do have cases like @jakearchibald demonstrates in https://github.com/w3c/csswg-drafts/issues/10334#issuecomment-2111871610 where we move an item from 1 container to another, and we want to contain the items moving to the second container that might be in a another tree. Here's an example where we move a group of items from 1 container to the other. We'd definitely use the `view-transition-parent` in this case: https://github.com/w3c/csswg-drafts/assets/23196205/bcee2114-c89c-42c1-8659-237ba06e0b29 I did have another use-case that I've been curious about, if we have the `view-transition-parent` set or just in general, it would be great to have access to the underlying data as well if we want to say animate a `clip-path` or do an offset within it. Something like `clip-path: inset(env(view-transition-parent-top) ...)`. Having access to _other_ ones would be great too but I realize that might be adding a lot of complexity. -- GitHub Notification of comment by calinoracation Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10334#issuecomment-2118219871 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 17 May 2024 19:05:58 UTC