The ViewTransition API allows authors to define visual transitions between 2 DOM states. The first phase of the feature is limited to transitions within the same Document initiated via a script API.
This feature is to support this API for DOM changes initiated via cross-document same-origin navigations.
This feature allows developers to add polished visual transitions to same-origin cross-document navigations. While creating this UX is possible for DOM changes within the same Document (Single-Page App), i'ts impossible for cross-Document navigations (Multi-Page App).
Initial public proposal
TAG review status
Interoperability and Compatibility
None. This feature is a progressive enhancement and authors can fallback to the current UX if the feature is not available.Gecko
: No signalWebKit
: No signalWeb developers
: Strongly positiveOther signals
WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
The feature can be debugged using standard tooling in devtools. Specifically the animation panel can be used to pause and scrub through the default animations set by the browser.
The pseudo DOM structure generated by the UA can also be inspected and targeted, like other DOM elements, in the style panel.
Requires code in //chrome?
No milestones specified
Link to entry on the Chrome Platform Status