You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: