- From: Ben Cole via GitHub <sysbot+gh@w3.org>
- Date: Tue, 03 Oct 2023 22:03:24 +0000
- To: public-css-archive@w3.org
+1 to optimizing the performance when there is no content change. I tested View Transitions in Chrome with a list of about 800 elements and found the performance to slow down a bit when starting transitions. Here's a fork of the Isotype style animation, with about 600 elements, to illustrate an extremely large number of elements being transitioned: https://codepen.io/bcole808/pen/VwqGoZm In this example, what I'm observing is that when clicking on one of the filters, there is a very long pause after the the pointer input occurs until the animation actually starts. Once the animation starts running, playback is pretty smooth. But the long pause before the animation starts makes it seem like there is a lot of work being done before it starts. Just showing the newly rendered element and applying a transition to the positioning (without a crossfade) is a common use case. So having a CSS property where developers can specify if there should be a crossfade from the old element to the new element sounds like a good idea. I agree that just tacking it onto `view-transition-name` seems weird (or perhaps there could be multiple CSS properties, and then there could be some shorthand way to specify all the values on one property). -- GitHub Notification of comment by bcole808 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9406#issuecomment-1745796786 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 3 October 2023 22:03:26 UTC