Intent to Ship: URLPattern ignoreCase

Skip to first unread message

Ben Kelly

Sep 28, 2022, 11:08:18 AM9/28/22
to blink-dev

Contact emails




Many client-side JavaScript frameworks currently use case insensitive URL matching. URLPattern, however, follows URL semantics and treats many parts of the URL as case sensitive. This feature adds an `ignoreCase` option to the URLPattern that switches all matching operations to case insensitive for that given pattern.

Blink component


TAG review

This is a very small addition to an existing API. I added a comment to the previous TAG review, but did not open a new TAG review for it. See:

TAG review status

Not applicable


Interoperability and Compatibility

The addition of the options dictionary argument is backward compatible. There should not be any web compat risk. No other browser has implemented URLPattern yet, so there is no interop risk. The polyfill has an open pull request to add the feature to it as well.

(Note, since this is a small addition to an existing API I posted comments on the existing position issues for the overall URLPattern API.)

Web developers: Positive ( This was a web developer community request and the spec/polyfill changes were contributed by an external web developer.

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?

This is a small addition that is wholly contained within blink. It should not pose any webview risk.


This is a small change to an existing API and does not require any devtools enhancements.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?


Is this feature fully tested by web-platform-tests?


Flag name

Requires code in //chrome?


Tracking bug

Estimated milestones

DevTrial on desktop107
DevTrial on Android107

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).

The spec changes have already landed. See:

Link to entry on the Chrome Platform Status

Links to previous Intent discussions

Intent to prototype:

This intent message was generated by Chrome Platform Status.

Philip Jägenstedt

Sep 28, 2022, 11:36:35 AM9/28/22
to Ben Kelly, blink-dev

The spec PR was merged and it's live here:

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
To view this discussion on the web visit

Chris Harrelson

Sep 28, 2022, 12:00:32 PM9/28/22
to Philip Jägenstedt, Ben Kelly, blink-dev

Yoav Weiss

Sep 28, 2022, 12:08:06 PM9/28/22
to Chris Harrelson, Philip Jägenstedt, Ben Kelly, blink-dev
Reply all
Reply to author
0 new messages