Contact emails [email protected], [email protected]
Explainer https://github.com/WICG/declarative-partial-updates/blob/main/route-matching-explainer.md#link-matching Specification https://drafts.csswg.org/css-navigation-1/#navigation-source-pseudo-class Summary Selects the element that initiated the navigation, whether it's a link/button/form. The element stays selected throughout the navigation. Blink component Blink>CSS Web Feature ID Missing feature Motivation The main motivation for this comes from view transitions. This gives author a way to visually indicate a relationship between the navigation source (form/button) and the process of the navigation, eg expanding a thumbnail using an animation. Initial public proposal https://github.com/w3c/csswg-drafts/issues/11801 TAG review No information provided TAG review status Pending Goals for experimentation None Risks Interoperability and Compatibility No information provided Gecko: No signal (https://github.com/mozilla/standards-positions/issues/1447) WebKit: No signal (https://github.com/WebKit/standards-positions/issues/715) Web developers: Strongly positive (https://adactio.com/links/22686) “I really, really, really like this proposal! This would absolutely turbo-charge cross-document view transitions with nary a line of JavaScript in sight.” (This is a view on the entire CSS Navigation Matching spec in total, not `:navigation-source` individually) 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? No information provided Debuggability No information provided 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 css/css-navigation/tentative/navigation-source-*.html Flag name on about://flags No information provided Finch feature name NavigationSourcePseudoClass Rollout plan Will ship enabled for all users Requires code in //chrome? False Tracking bug https://issues.chromium.org/issues/530210946 Estimated milestones Shipping on desktop 156 Shipping on Android 156 Shipping on WebView 156 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/6327898878377984?gate=6247925882683392 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 [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a9941cf.aec07b4f.8d5be.0061.GAE%40google.com.
