Did you know it's called the View Transition API (and not the View Transitions API [plural])? Now MDN knows too (github.com/mdn/content/...) so there's no reason to keep using the wrong name. Learn about this and other misconceptions in this post: developer.chrome.com/blog/view-tr...
Post
developer.chrome.comMisconceptions about view transitions | Blog | Chrome for DevelopersWith more and more people starting to look into the View Transition API, it's time to debunk some misconceptions.
Yes, but if you insert/remove an item into it and want others to animate, doing that for each item separately is very unoptimized. In this simple card demo style recalc on each frame grows from 0.2ms for 5 items to 3ms for 75 items view-transitions.chrome.dev/cards/spa/
view-transitions.chrome.devBoxes
You can apply the same optimization to the View Transitions-powered implementation: wrap things in a div and give the wrapper a view-transition-name. (But do know that this workaround only works when things don't reflow)
0 reposts1 like
No replies yet.