If you want to use multi-page view transitions, this used to be a prerequisite:
<meta name="view-transition" content="same-origin">
Code language: HTML, XML (xml)
That’s dead. Now you do this:
@view-transition {
navigation: auto;
}
Code language: CSS (css)
Thanks to Bramus for the PSA and update article.
I imagine we’ll see PRs a lot like this!
![](https://i0.wp.com/frontendmasters.com/blog/wp-content/uploads/2024/05/Screenshot-2024-05-30-at-8.49.00%E2%80%AFAM-1024x760.png?resize=1024%2C760&ssl=1)
Real quick here, I think the new Speculation Rules API is worth a mention. See, there is an immediate performance cost to using multi-page view transitions. In order for the browser to understand what and how to transition, it needs to essentially render the page you are navigating to behind-the-scenes, then navigate to it, causing a bit of a delay. Hopefully that’s mitigated by the transition itself a bit, but any performance hit sucks. If the page was already pre-rendered (like it might be with this new API available), it should be smooth as butter.