Intent to Prototype: View Transitions: transition types

[Vladimir Levin]

Contact emails

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

Specification

https://drafts.csswg.org/css-view-transitions-2/#the-active-view-transition-pseudo

Summary

This feature allows View transition API use to be customized for different types of transitions. Specifically, this adds an ability to add "types" to `startViewTransition` call which will identify the types of the transition. As well, it will match a pseudo-class, called `:active-view-transitions(...)` with a parameter matching the type for the duration of the view transition. Combined these two features provide a way for the author to declare several view transitions once and only trigger one at a time. See example usage in the spec: https://drafts.csswg.org/css-view-transitions-2/#the-active-view-transition-pseudo

Blink component

Blink>ViewTransitions>SPA

TAG review

None

TAG review status

Not applicable

Risks

Interoperability and Compatibility

None, this builds on top of existing ViewTransitions API, but doesn't break existing behavior.

Gecko: No signal

WebKit: No signal

Web developers: No signals

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, WPTs will come as part of implementation

Flag name on chrome://flags

None

Finch feature name

ViewTransitionTypes

Non-finch justification

None

Requires code in //chrome?

False

Tracking bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1466251

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5089552511533056

This intent message was generated by Chrome Platform Status.