Chrome has renewed work on native page transitions, with a new WICG repository for the proposal and a build available to try today in Chrome Canary.
Would you like to add navigation transitions to your site without making your site an SPA? Then give this issue a thumbs-up: https://t.co/iEv7lV5u27
— Jake Archibald (@jaffathecake) April 26, 2021
Moving elements, not just whole pages
The "shared element" framing is the key idea: this is not limited to a slide-out/slide-in or a star wipe. Individual elements can be animated to new positions across a navigation. Sarah's article was highlighted as a clear demonstration of that capability.
https://twitter.com/sarah_edo/status/988414671232339970
The current README carries a code sample showing the approach in use.
function handleTransition() {
document.documentTransition.prepare({
rootTransition: "reveal-left",
duration: 300,
sharedElements: [e1, e2, e3]
}).then(() => {
doCustomThings();
document.documentTransition.start({ sharedElements: [newE1, newE2, newE3] }).then(
() => console.log("transition finished"));
});
}
Shared elements are optional, but when they are declared, each one currently requires contain: paint in CSS. According to the proposal's author, URL updates need no developer handling, since the model does not depend on a single-page app architecture.
Older platform precedent
Pre-Chromium Edge had its own proprietary page transition filters.
<meta http-equiv="Page-Enter"
content="RevealTrans(Duration=0.600, Transition=6)">
Christian Schaefer's post on the end of the Trident era discusses what that legacy provided. As the term suggests, these filters moved the user smoothly from page to page during navigation rather than the abrupt page appearance we are accustomed to, chosen by number from an extensive list of transition filters.
The list included wipes up and down, random dissolves and horizontal splits, but no star wipes and no shared-element transitions.



