Intent to Prototype: Declarative route matching

[Chromestatus]

Contact emails

nrose...@chromium.org, mste...@chromium.org, foo...@chromium.org

Explainer

https://github.com/WICG/declarative-partial-updates?tab=readme-ov-file#part-2-route-matching

Specification

None

Summary

A "route" is a URL pattern that has rules attached to it. Allow developers to respond to URL changes by assigning names to routes and matching them directly with CSS or with JS.

Blink component

Blink>HTML

Motivation

Today, anything to do with URL changes, such as hiding/showing parts of the DOM based on the URL, is done with script. On top of that, same-document navigations and almost any meaningful interaction that doesn't refresh the whole page is reliant on imperative scripting. This prototyping explores whether introducing routing into the web platform provides value in itself and/or as a foundation for some form of a more integrated experience declarative same-document navigation alongside the highly customizable JS environment.

Initial public proposal

https://github.com/WICG/proposals/issues/216

TAG review

None

TAG review status

Pending

Risks

Interoperability and Compatibility

None

Gecko: No signal

WebKit: No signal

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 about://flags

None

Finch feature name

None

Non-finch justification

None

Requires code in //chrome?

False

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/4771962874363904?gate=5917641910517760

This intent message was generated by Chrome Platform Status.