The `startViewTransition` call currently takes an optional nullable callback type with a default value of null: `startViewTransition(optional UpdateCallback? callback = null)` This feature changes this to be a non-nullable type: `startViewTransition(optional UpdateCallback callback)` More details: https://github.com/w3c/csswg-drafts/issues/9460
If there are cases of startViewTransition that explicitly pass `null` then these will stop working. We don't believe there is any significant number of these, based on the currently low usage of the view transition API, and null being a small subset of those.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
Same as ViewTransitiosn
Shipping on desktop | 120 |
Shipping on Android | 120 |
Shipping on WebView | 120 |
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