-
Notifications
You must be signed in to change notification settings - Fork 74
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
ServiceWorker static routing API #828
Labels
Comments
This was referenced Jun 19, 2023
asutherland
added a commit
to asutherland/standards-positions
that referenced
this issue
Sep 28, 2023
asutherland
added a commit
to asutherland/standards-positions
that referenced
this issue
Sep 29, 2023
martinthomson
pushed a commit
that referenced
this issue
Sep 29, 2023
FYI, I just merged the spec PR for this. Happy to take any additional feedback you might have into account though. |
(Implementation bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1855580) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Request for Mozilla Position on an Emerging Web Specification
Specification Title: ServiceWorker static routing API
Specification or proposal URL (if available):
Explainer URL (if available): https://github.com/yoshisatoyanagisawa/service-worker-static-routing-api
Caniuse.com URL (optional):
Bugzilla URL (optional):
Mozillians who can provide input (optional):
Other information
This API allows developers to configure the routing, and allows them to offload simple things ServiceWorkers do. If the condition matches, the navigation happens without starting ServiceWorkers or executing JavaScript, which allows web pages to avoid performance penalties due to ServiceWorker interceptions.
Starting ServiceWorkers is known to be a slow process, and web users need to wait for its startup if the ServiceWorker intercepts loading the page resources. At the same time, the ServiceWorker brings flexibility to the transport layer, and it behaves as a client-side proxy. Developers can implement offline support or provide client-side content modification with it. Currently, ServiceWorkers intercept all requests for pages within their scope, which brings a performance penalty within the scope.
The text was updated successfully, but these errors were encountered: