Intent to Ship: View Transitions Same-Origin Navigation
Khushal Sagar
Contact emails
bo...@google.com, khusha...@google.com, nrose...@google.com, vmp...@google.com
Explainer
https://github.com/WICG/view-transitions/blob/main/cross-doc-explainer.md
Specification
https://drafts.csswg.org/css-view-transitions-2
https://github.com/w3c/transitions/issues/595 tracks publishing a FPWD for this spec based on the resolution here.
Summary
The first phase of the View Transitions API, shipped here, allows authors to define visual transitions in SPAs (DOM state changes in the same Document).
This intent is about expanding the API to support MPAs. MPA implies same-origin navigations that replace the document with another document (in the main frame or nested iframe).
This is a highly requested additional feature. Examples are: https://chriscoyier.net/2022/11/08/astro-stands-to-benefit-highly-from-view-transitions/, https://adactio.com/journal/19578.
Blink component
TAG review
https://github.com/w3ctag/design-reviews/issues/851
TAG review status
Issues addressed
Risks
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: Positive (https://github.com/mozilla/standards-positions/issues/677#issuecomment-1567988287)
WebKit: No signal (https://github.com/WebKit/standards-positions/issues/302)
Web developers: Strongly 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
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.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
Yes
Is this feature fully tested by web-platform-tests?
Yes
Flag name on chrome://flags
view-transition-on-navigation
Finch feature name
ViewTransitionOnNavigation
Requires code in //chrome?
False
Tracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=1372584
Estimated milestones
Note: We plan to roll out the feature via finch to monitor for stability issues. 126 is the target milestone for roll out to beta; before shipping to stable in 127.
Anticipated spec changes
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
None
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5118874666663936?gate=5059113954836480
Links to previous Intent discussions
Intent to prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMLuWUxMPaChgK0VH6cZNY_LE68zNQ-NTxA7DFzd-7PjyKi1Dw%40mail.gmail.com
This intent message was generated by Chrome Platform Status.
Alex Russell
Chris Harrelson
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/99e5800a-3ef4-47ec-a0d7-de1308bdc5d7n%40chromium.org.
Mike Taylor
LGTM3
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw-L%2BVU1PVQOdLFophPPEifm%3DHVMpeWeejQOUMF2_UY2JQ%40mail.gmail.com.