Contact emails
nrosent...@chromium.org, vmp...@chromium.org

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


Specification
https://drafts.csswg.org/css-view-transitions-2/#auto-vt-name


Summary

This intent covers two new keywords for view-transition-name: - 'match-element' 
generates a unique id based on the element's identity and renames the same for 
this element. This is used in Single Page App cases where the element is being 
moved around and the desire is to animate it with a view transition - 'auto' 
generates a unique id based on the element's id attribute. This value remains 
the same for the same ids regardless of the element, but does not otherwise 
match the view-transition-name named with the same ident as the id. This can be 
used in both Single and Multi Page Apps to match elements based on their id 
attributes. 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


TAG review
https://github.com/w3ctag/design-reviews/issues/1001


TAG review status
Issues addressed


Risks




Interoperability and Compatibility

None


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

WebKit: Shipped/Shipping 
(https://webkit.org/blog/16301/webkit-features-in-safari-18-2)

Web developers: Positive This is a highly requested feature to prevent the need 
to uniquely identify each participating view transition element.

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



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/auto-name-from-id.html?label=experimental&label=master&aligned
 
https://wpt.fyi/results/css/css-view-transitions/navigation/auto-name-from-id.html?label=experimental&label=master&aligned



Flag name on about://flags



Finch feature name
CSSViewTransitionAutoName


Requires code in //chrome?
False


Tracking bug
https://issues.chromium.org/issues/399877975


Estimated milestones


Shipping on desktop 136

Shipping on Android 136

Shipping on WebView 136




Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop 
issues. Please list open issues (eg links to known github issues in the project 
for the feature specification) whose resolution may introduce web 
compat/interop risk (eg, 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/6575974796492800?gate=5170335230722048


Links to previous Intent discussions
Intent to Prototype: 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/66fe6d9c.2b0a0220.d54b7.1136.GAE%40google.com



This intent message was generated by Chrome Platform Status.

-- 
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+unsubscr...@chromium.org.
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/67dc67cf.170a0220.1d1eca.05f6.GAE%40google.com.

Reply via email to