Contact emailsvmp...@chromium.org, nrosent...@chromium.org ExplainerNone
Specificationhttps://drafts.csswg.org/css-view-transitions-2/#auto-vt-name Summary '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 Note this is split off from https://chromestatus.com/feature/6575974796492800 which contains additional discussions Blink componentBlink>ViewTransitions>SPA <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EViewTransitions%3ESPA%22> TAG reviewhttps://github.com/w3ctag/design-reviews/issues/1001 TAG review statusIssues addressed. Note that TAG discussion continues about view-transition-name: auto which will be tracked in a separate intent. Risks Interoperability and Compatibility None *Gecko*: No signal ( https://github.com/mozilla/standards-positions/issues/1198) *WebKit*: Shipped/Shipping ( https://developer.apple.com/documentation/safari-release-notes/safari-18_4-release-notes ) *Web developers*: Positive This is a developer request feature to ensure that they do not have to come up with unique names for every participating 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)?No Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ?Yes https://wpt.fyi/results/css/css-view-transitions/match-element-name.html?label=master&label=experimental&aligned Flag name on about://flagsNone Finch feature nameCSSViewTransitionMatchElement Requires code in //chrome?False Estimated milestones Shipping on desktop 137 Shipping on Android 137 Shipping on WebView 137 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). None Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5098745710247936?gate=5195081088499712 This intent message was generated by Chrome Platform Status <https://chromestatus.com/>. -- 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/CADsXd2MKDKqxQmkK%2B-m_gjnVJrVUGnBUniaOVDYbM6FZPQhwwQ%40mail.gmail.com.
