Intent to Prototype: Auto-generated view transition names

[Chromestatus]

Contact emails

nrose...@chromium.org

Explainer

https://github.com/WICG/view-transitions/blob/main/auto-name-explainer.md

Specification

https://github.com/w3c/csswg-drafts/pull/10922

Summary

Allow the 'auto' keyword as a value for the 'view-transition-name' CSS property. This generates a unique name for the element, and reduces the burden of having to invent unique names for participating elements.

Blink component

Blink>CSS

Motivation

Reducing the burden of inventing unique names for view transitions has been a major complaint around view transitions. One of the major use cases was this was single-page transitions, such as animated grid sorting, where the elements remain stable but use view transitions to animate their states. By using 'view-transition-name: auto' we leave the name generation to the browser in those cases.

Initial public proposal

https://github.com/w3c/csswg-drafts/issues/8320#issuecomment-2344208387

TAG review

None

TAG review status

Pending

Risks

Interoperability and Compatibility

None

Gecko: No signal

WebKit: No signal This was originally proposed by WebKit

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

Flag name on chrome://flags

None

Finch feature name

None

Non-finch justification

None

Requires code in //chrome?

False

Tracking bug

https://issues.chromium.org/issues/365997248

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/6575974796492800?gate=5009628023488512

This intent message was generated by Chrome Platform Status.