- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Jul 2024 18:54:41 +0000
- To: public-css-archive@w3.org
> @noamr One potential issue I see with that is we've typically relied on the `::view-transition-old:only-child` selector to have a meaning of enter/exit based on if it's on the new or old element. This would seemingly create an exception for this use case where we'd have to do something different to accomplish that if I'm understanding correctly. It's not exactly an exception, I see these as actual exit/entry transitions, except there is some default relationship (e.g. the default transform animation would map to the same position on the screen) > How would we work around that as far as letting people still differentiate when something has been split into exclusive groups or if it really was just entering or exiting? One way is to not use this feature of mismatching groups :) It's a totally optional thing and an author can mandate using a common ancestor or flat tree etc. Another way is to add a `view-transition-class` that differentiates between the two. Are these mechanisms sufficient perhaps? -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10334#issuecomment-2223670284 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 11 July 2024 18:54:42 UTC