Intent to Prototype: Two-phase cross-document view transition

[Chromestatus]

Contact emails

nrose...@chromium.org, vmp...@chromium.org

Explainer

https://github.com/w3c/csswg-drafts/blob/main/css-view-transitions-2/two-phase-transition-explainer.md

Specification

None

Summary

Currently, cross-document view transitions are only captured when the new document's response arrives, and activated only when the new document is ready to render a frame. This delay, when long, can cause a jarring experience. Two-phase view transitions allow starting a same-document view transition when the navigation start, with a guarantee that it will continue to the end without an abrupt cancellation due to a race with the navigation commit, as long as it is ready to present frames before the commit.

Blink component

Blink>CSS

Web Feature ID

view-transitions

Motivation

We are not sure if this requires a spec change yet or it can be done as an internal scheduling improvement. Some prototyping should help clarify that and would feed into whether a spec proposal is needed.

Initial public proposal

https://github.com/w3c/csswg-drafts/issues/12829

TAG review

None

TAG review status

Pending

Risks

Interoperability and Compatibility

None

Gecko: No signal

WebKit: No signal

Web developers: Positive

Other 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? None

Debuggability

None

Is this feature fully tested by web-platform-tests?

No

Flag name on about://flags

None

Finch feature name

None

Non-finch justification

None

Requires code in //chrome?

False

Tracking bug

https://issues.chromium.org/issues/445771450

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5568746374692864?gate=5140041898786816

This intent message was generated by Chrome Platform Status.