Closed
Bug 1219072
Opened 9 years ago
Closed 5 years ago
Use a Service Worker to Cache Frequently Used Resources
Categories
(developer.mozilla.org Graveyard :: General, enhancement)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: davidwalsh, Unassigned)
Details
(Keywords: in-triage, Whiteboard: [specification][type:feature])
What problem would this feature solve?
======================================
We could make MDN's front end significantly faster with front-end assets using a Service Worker. Files could include:
* CSS Files
* JS Files
* Fonts
* Design images
We do a great job with minification and async'ing of resources right now but a Service Worker would save numerous requests and downloads.
Who has this problem?
=====================
All visitors to MDN
How do you know that the users identified above have this problem?
==================================================================
Because we aren't using Service Workers.
How are the users identified above solving this problem now?
============================================================
They aren't; even when a file is in cache, a request is made to the server to check cache status.
Do you have any suggestions for solving the problem? Please explain in detail.
==============================================================================
We can implement a Service Worker with cache-busting capabilities (either by version or by expiration) for clients with adequate fetch and navigator.serviceWorker features.
Is there anything else we should know?
======================================
Comment 1•5 years ago
|
||
MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•