The URL Pattern API allows developers to specify pattern strings. Those are transformed to regular expressions internally. When the API was first implemented, these regular expressions were compiled with the u flag. We're going to update it to the v flag, enabling Unicode sets.
https://github.com/tc39/proposal-regexp-v-flag#how-is-the-v-flag-different-from-the-u-flag This doc has a list the potentially breaking changes between u and v. Some patterns that previously would compile, now throw an error with the v flag, specifically those with a character class including either an unescaped special character or a double punctuator. I believe it does not significantly affect the patterns in use today. From UMA metric on Beta, incompatible patterns are less than 0.001% of the total compilation. Also, the use counter of the API itself has only 0.11%. The expected impact is extremely limited.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
https://wpt.fyi/results/urlpattern/urlpattern.any.html Tests for set notations were added in https://github.com/web-platform-tests/wpt/pull/43014
Shipping on desktop | 121 |
Shipping on Android | 121 |
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--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGMyg-ZAnsDEw1haRd1HOuYcieHOYKZ73oYAQ3SfWv9umsd-TA%40mail.gmail.com.
Filed an issue, I'm happy to work on it.Thank you for the heads up!
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGMyg-ZAnsDEw1haRd1HOuYcieHOYKZ73oYAQ3SfWv9umsd-TA%40mail.gmail.com.
This feels like something that has the potential to be rather thorny... I would expect 0.001% on Beta to be higher on Stable.
Given that your UMA
landed in M120, could we wait a few weeks to look at the stable
data, then come back with an Intent to Ship? This seems slightly
riskier for a page than
https://groups.google.com/a/chromium.org/g/blink-dev/c/gIyvMw0n2qw/m/-WZC9C4VCQAJ
(which had server-side validation as a fallback).
--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/c16d70b8-298a-4dc7-80cf-1c1c2ae5c8ab%40chromium.org.
"Will this feature be supported on all six Blink platforms" I see the answer is no. Which platforms are not going to be supported?
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGMyg-bf%2Bup%3DecrFxQNYnXe%3DzW9tHOajJMmbYUt6hbi9BD17_w%40mail.gmail.com.
In case helpful: the earlier i2s for html-pattern-v has some compat data on the specific case of upgrading the HTML `pattern` attribute from the `u` to the `v` flag: https://groups.google.com/a/chromium.org/g/blink-dev/c/gIyvMw0n2qw/m/3XaP6hFpAgAJOn Thu, Nov 16, 2023 at 5:55 AM Shunya Shishido <sisid...@chromium.org> wrote:We can wait for more data from the upcoming M120 stable for more confidence, but in that case we need an Intent to Ship instead of this PSA?As Jeremy mentioned the actual usage is nearly zero, so I believe this change very unlikely breaks sites.
On 11/16/23 11:22 AM, Jeremy Roman wrote:
On Thu, Nov 16, 2023 at 1:26 AM Mathias Bynens <mat...@chromium.org> wrote:
In case helpful: the earlier i2s for html-pattern-v has some compat data on the specific case of upgrading the HTML `pattern` attribute from the `u` to the `v` flag: https://groups.google.com/a/chromium.org/g/blink-dev/c/gIyvMw0n2qw/m/3XaP6hFpAgAJ
On Thu, Nov 16, 2023 at 5:55 AM Shunya Shishido <sisid...@chromium.org> wrote:
We can wait for more data from the upcoming M120 stable for more confidence, but in that case we need an Intent to Ship instead of this PSA?
As Jeremy mentioned the actual usage is nearly zero, so I believe this change very unlikely breaks sites.
Also worth noting this feature is Finchable, so in the unlikely event we see a spike in this in stable, we can Finch it off to reconsider before enabling this by default hits the stable channel.