Intent to Ship: ViewTransitions waitUntil() method

[Chromestatus]

Contact emails

vmp...@chromium.org

Explainer

https://github.com/vmpstr/htmldemos/blob/master/vt/waitUntil.md

Specification

https://drafts.csswg.org/css-view-transitions-2/#dom-viewtransition-waituntil

Summary

The ViewTransition automatically constructs a pseudo-element tree to display and animate participating elements in the transition. Per spec, this subtree is constructed when the view transition starts animating and is destroyed when the animations associated with all view transition pseudo-elements are in the finished state (or more precisely in a non-running non-paused state). This works for a vast majority of cases and provides a seamless experience for the developers. However, for more advanced cases, this is insufficient as there are times when developers want the view transition pseudo-tree to persist beyond the animation finish state. One example is tying view transitions with Scroll Driven Animations. When the animation is controlled by a scroll timeline, we don't want the subtree to be destroyed when the animations finish since scrolling back should still be able to animate the pseudo elements. In order to enable advanced uses of view transition, this intent adds a waitUntil() function on the ViewTransition object which takes a promise. This promise then delays destruction of the pseudo-tree until it is settled.

Blink component

Blink>ViewTransitions

Web Feature ID

view-transitions

Motivation

No information provided

Initial public proposal

https://github.com/w3c/csswg-drafts/issues/9901#issuecomment-2165674531

TAG review

https://github.com/w3ctag/design-reviews/issues/1158

TAG review status

Pending

Risks

Interoperability and Compatibility

No information provided

Gecko: No signal (https://github.com/mozilla/standards-positions/issues/1309)

WebKit: No signal (https://github.com/WebKit/standards-positions/issues/564)

Web developers: Positive (https://github.com/w3c/csswg-drafts/issues/9901#issuecomment-1927103230)

Other signals:

Ergonomics

None

Activation

None

Security

None

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?

No information provided

Debuggability

This feature can be debugged with the existing devtools functionality

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
https://wpt.fyi/results/css/css-view-transitions/view-transition-waituntil-animation-manipulation.html?label=experimental&label=master&aligned

Flag name on about://flags

No information provided

Finch feature name

ViewTransitionWaitUntil

Rollout plan

Will ship enabled for all users

Requires code in //chrome?

False

Tracking bug

https://issues.chromium.org/346976175

Estimated milestones

Shipping on desktop	143
Shipping on Android	143
Shipping on WebView	143

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).

No information provided

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/4812903832223744?gate=4866081432928256

This intent message was generated by Chrome Platform Status.

[Chris Harrelson]

LGTM1

--
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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68f79e94.050a0220.39dfc1.07d7.GAE%40google.com.