- From: Tim Nguyen via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 May 2024 09:29:34 +0000
- To: public-css-archive@w3.org
With `view-transition-tree: preserve | flatten` it's unclear to me whether what container to apply it on, or even if it applies to the container or the child in the first place.
`view-transition-parent: <name> | auto | none` is better in terms of use-case coverage, but the main issue is circularity (`.child { view-transition-parent: parent; } .parent { view-transition-parent: child }`), it would be good to avoid this footgun.
I don't have great suggestions on top of my head, but could the use cases be covered by scoped element transitions? e.g. making so running a document VT + a scoped element transition concurrently parents things accordingly? or having some API to run both at the same time?
--
GitHub Notification of comment by nt1m
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10334#issuecomment-2112023977 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 May 2024 09:29:35 UTC