- From: Bramus via GitHub <noreply@w3.org>
- Date: Mon, 30 Jun 2025 08:52:55 +0000
- To: public-css-archive@w3.org
The tricky part here is that you would not only need to define the exit-styles but also need to: - Define on which part of the tree you want to run the View Transition: the direct parent or some other ancestor? - Determine which elements get a `view-transition-name` as part of that mutation. - Need to figure out whether the removed element also gets a (special) `view-transition-name` or not, and what to do with the exit-styles in case of conflict. Also not covered are batched updates – such as multiple elements getting removed at once or elements getting removed in once place and added in a new place (for which one should use [`moveBefore`](https://brm.us/movebefore)). Perhaps some automatically generated types on the VT object could aid with some of that, but I haven’t explored that. Side Note: In https://codepen.io/bramus/pen/zxOOzYX I have an exploration that automatically wraps a removal of a node in a View Transition. It’s using a `MutationObserver` to undo and then redo the mutation. See https://brm.us/auto-transitions for a full write-up. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9500#issuecomment-3018331331 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 30 June 2025 08:52:55 UTC