- From: Kevin Doughty via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Apr 2024 22:08:51 +0000
- To: public-css-archive@w3.org
Sort function. For sub-elements not handled at the current level, return null instead of 1, 0, or -1. That means a different invocation of startViewTransition, with a corresponding different pseudo-element, has provided the sort for the sub-element. To animate back in a sub-element of an element being animated out, a rasterized representation of the group would have to be redrawn with the sub-element removed from the picture. That group would have to be kept in memory, just inaccessible to the page author, for the duration of the exit animation. Styles would have to be preserved too. I hope those are what are called "snapshots" in Firefox/Servo, and they're not rasterized images. Styles of these snapshots would not have to be recalculated but the sub-element’s snapshot would have to be removed. Yes it’s hairy. Exit animations on the group would have to be copied from the group to the newly reinserted sub-element. A fade out animation continues to run, and a new fade in animation runs additively on top. Also, elements animating in should be live and instantly accessible to events. If discrete-state were implemented, hit testing would always resolve to destination values regardless of animation state. No blocking the UI please. -- GitHub Notification of comment by KevinDoughty Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9578#issuecomment-2075936541 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 April 2024 22:08:52 UTC