Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

At-risk feature: tab_strip scope_patterns accepting a string #97

Open
mgiuca opened this issue Apr 19, 2024 · 0 comments
Open

At-risk feature: tab_strip scope_patterns accepting a string #97

mgiuca opened this issue Apr 19, 2024 · 0 comments

Comments

@mgiuca
Copy link
Member

mgiuca commented Apr 19, 2024

The scope_patterns member is parsed using URLPattern's build a URL pattern from an infra value, which accepts the URL pattern as either a string or a map containing URL pattern components.

Currently, no implementation accepts the string form. (As there is only one implementation, Chromium, and it does not currently support the string form. Chromium tracking bug: crbug/330640840).

We could change the spec to expect only a map, but it would be a shame, as the string form is much easier to use, and the URLPattern spec explicitly says that JSON-based usages should use this algorithm. So for now, keeping it in the spec but acknowledging it is at risk.

If this becomes supported, the usage example should be updated to use the more natural string syntax.

@mgiuca mgiuca changed the title tab_strip scope_patterns parsing as a string is "at risk" At-risk feature: tab_strip scope_patterns accepting a string Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant