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

pass patterns as strings to service worker API #21

Closed
wanderview opened this issue Oct 13, 2020 · 1 comment
Closed

pass patterns as strings to service worker API #21

wanderview opened this issue Oct 13, 2020 · 1 comment
Labels
decided topic: service worker Related to integration of URL patterns and service workers

Comments

@wanderview
Copy link
Member

Per discussions leading up to w3c/ServiceWorker#1468 (comment) there is a growing consensus that patterns should be passed to the service worker API as strings and not objects.

While that integration will ultimately be spec'd in the service worker repo I'm filing an issue here to track it and for eventually updating the explainer.

@wanderview wanderview added the topic: service worker Related to integration of URL patterns and service workers label Aug 12, 2021
@sisidovski
Copy link
Collaborator

ServiceWorker Static Routing API provides a way to bypass service worker in some specific URLs in the registered scope.

If the scope pattern matching for the service worker registration is required for the bypassing purpose, it can achievable by the the static routing API. The example in the explainer describes how to bypass SW on pages in the scope.

I'll close this issue but feel free to reopen if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
decided topic: service worker Related to integration of URL patterns and service workers
Development

No branches or pull requests

2 participants