Cross-document View Transitions are an extension to same-document transitions, adding the semantics necessary to display transitions when navigating across documents.
The main explainer and the css-view-transitions-1 spec
provide a detailed explanation about same-document view transitions. Most of that is applicable to
cross-document transitions as well. This document provides explanations about the additional
semantics, and how cross-document transitions work.
Developers shouldn't have to jump through hoops or rethink their transition design when switching between an MPA architecture and an SPA architecture. The main building blocks of the transition, the way the states are captured, the way the captured images are animated, and the JavaScript API, should remain the same, as much as possible.
Unlike same-origin transitions, Cross-document transitions should work automatically without JavaScript intervention. They should provide the right CSS & JavaScript knobs for when the defaults are not enough.
Cross-document view transitions are only enabled for same-origin navigations without a cross-origin redirect. In the future we could examine relaxing this restriction in some way to same-site navigations. Cross-site view transitions are a non-goal.
Both the old and new document need to declaratively opt-in to the transition between them. If both opted in, and this is a same-origin navigation without cross-origin redirects, the state of the old document is captured, using the same algorithm used for same-document transitions.
When the new document is about to present the first frame, i.e. when the document is no longer render blocked or at the course of reactivation from prerendering/back-forward cache, the state of the new document is captured, also using the equivalent algorithm.
If all conditions are met and both states are captured, the transition proceeds to update the pseudo element styles and display the animation, as if it was a same-document transition.
The new document can customize the style of the animation using the same CSS techniques available for same-document transitions. Both documents can interrupt the transition in different phases, or observe its completion.
So to support cross-document view transition, the following things need to be specified:
- A way for both documents to opt in to the transition.
- The lifecycle: the exact moments in which the states are captured.
- A JavaSript API to control the animation, equivalent to how same-document animations can be controlled.
w3c/csswg-drafts#8048
w3c/csswg-drafts#9534
w3c/csswg-drafts#8783
To enable cross-document transitions, the old and new documents need to be coordinated with each other - as in, the transition names in the old document match the ones in the new document and the effect of animating between them is intentional. Otherwise, there could be a situation where two documents of the same origin define styles for same-document transitions independently, and enabling this feature would create an unexpected transition between them.
This is an issue that is specific to cross-document transitions, as same-document transitions are triggered imperatively in the first place.
The minimal functional opt-in would be a global declaration that the document supports view transitions:
@view-transition {
navigation: auto;
}Opts a document in to transitions for navigations that are:
- push or replace, excluding reloads, and not from browser UI
- history traversal, with or without user involvement
@view-transition can be nested within conditional group rules to e.g.
conditionally opt-out depending on reduced-motion preferences:
@view-transition {
navigation: auto;
}
@media (prefers-reduced-motion) {
@view-transition {
navigation: none;
}
}
The old state is captured right before the old document is hidden and a new one is shown. In the HTML spec that moment is defined here. This can either happen during normal navigations, when the new document is about to be created, in Back/Forward cache navigations, or when activating a prerendered document.
Before creating the new document (or activating a cached/prerendered one), the UA would update the rendering and snapshot the old document, in the same manner a document is snapshotted for a same-document navigation.
The new state is captured right before the first rendering opportunity of the new document. This allows the new document to use the render-blocking mechanism as a way to delay the transition.
As shown in the chart above, that first rendering opportunity can come in two cases, either it's a newly initialized document that's no longer render-blocked, or it's a document that's been frozen due to back-forward cache or prerendered, and is now being activated.
Note: relying on the render-blocking mechanism is limited, as only a limited set of elements participate in that mechanism. See proposal to extend it.
To fullfill the design principle of making cross-document transitions compatible with same-document transitions, cross-document transition need to be as customizable as same-document transitions, while allowing good defaults that work declaratively.
Same document transitions can be programatically extended (until the updateCallbackDone promise is fullfilled), skipped, programatically animated using the ready promise, and their end time can be observed.
To achieve the same level of control for cross document navigations we propose two new events, corresponding to last pre-snapshot moment in the old and new documents.
Authors need some point in an outgoing document to customize or skip the cross-document transition.
This is provided by the pageswap event. This event is fired when a
document is about to be unloaded due to a navigation, and contains the origin-accessible activation info for the next document. If this navigation triggers a view-transition due to a @view-transition rule, the event's viewTransition property would be a ViewTransition object (otherwise it will be null).
Note that this event is different from pagehide
in the case where a view-transition is present. In that case, pageswap would be fired before the document is hidden, deferring activation of the new document in favor of a final rendering update to capture the old state for the view-transition.
When the navigation is not eligible for view-transitions (it's cross-origin, or its navigation type doesn't match the @view-transition rule), pageswap is fired right before pagehide, but only for the navigating document. Its iframes, or documents that are unloaded without a navigation, don't receive a
pageswap event.
A pageswap event has a NavigationActivation property activation. This is handy for making decisions about skipping/customizing the transition based on the old/new URL or navigation type. Note that the new URL here is the final URL after redirects. The activation property is null for cross-origin navigations.
window.addEventListener("pageswap", event => {
if (!event.viewTransition) {
return;
}
const from_path = new URL(event.activation.from).pathname;
const to_path = new URL(event.activation.entry).pathname;
// Skip transitions from landing home
if (from_path === "/landing" && to_path === "/home")
event.viewTransition.skipTransition();
// Apply a different style when going "back"
const is_back = event.activation.navigationType === "traverse" &&
event.activation.entry?.index === (event.activation.from?.index - 1);
// Note that this would only apply to capturing the final state of the old document,
// The new document would have to do this or something similar in `pagereveal`.
document.documentElement.classList.toggle("back-nav", is_back);
});See ongoing discussion at whatwg/html#9702.
See revealing the document in the HTML spec.
To allow customizing a view transition from the new document, fire a pagereveal event at the first render opportunity when loading or activating (from BFCache/prerender) a document.
If a view transition was started by the old document, pagereveal will provide the ViewTransition object.
Note that this event is different from pageshow as
a newly initialized document fires pageshow is only once the document is fully loaded.
window.addEventListener("pagereveal", event => {
if (!event.viewTransition)
return;
const from_path = new URL(navigation.activation.from).pathname;
// Skip transitions from home
if (from_path === "/home")
event.viewTransition.skipTransition();
// Apply a different style when going "back"
const is_back = navigation.activation.navigationType === "traverse" &&
navigation.activation.entry?.index === (navigation.activation.from?.index - 1);
document.documentElement.classList.toggle("back-nav", is_back);
});See the list of open issues labeled css-view-transitions-2 for the up-to-date list of issues, and w3c/csswg-drafts#8804 for the main discussion about
cross-document transitions.