Cross-Document View Transitions for MPA: you need @view-transition to opt-in, not the meta tag

Promotional screenshot as used on social media (tweet, toot)


📣 PSA: Time to update your MPA View Transitions experimentations!

The opt-in for Cross-Document View Transitions for MPAs (aka: “just websites”) is by means of the @​view-transition at-rule in CSS.

@view-transition {
  navigation: auto;

This opt-in needs to be present on both pages participating in the View Transition.

The meta tag that you might know from before was a temporary thing while the feature was being developed behind a flag. The meta tag no longer does anything and was removed in Chrome 125, it’s the CSS opt-in that you need.

Cross-Document View Transitions are shipping to stable (read: enabled by default for all users) in Chrome 126.

If you haven’t been following, there’s also two new things that you can use with View Transitions nowadays:

1. View Transition Types
2. view-transition-class

See for an overview (text + video) of all additions and improvements.


Spread the word

Feel free to repost one of the posts from social media to give them more reach, or link to this post from your own blog.


Published by Bramus!

Bramus is a frontend web developer from Belgium, working as a Chrome Developer Relations Engineer at Google. From the moment he discovered view-source at the age of 14 (way back in 1997), he fell in love with the web and has been tinkering with it ever since (more …)

Unless noted otherwise, the contents of this post are licensed under the Creative Commons Attribution 4.0 License and code samples are licensed under the MIT License

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.