Auto-update offline service-worker
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 233
- Forks
- 61
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 82
Description
Follow up to https://github.com/mdn/fred/issues/525
When testing the yari -> fred offline migration, I noticed that blink and webkit based browsers appeared to update the service worker in the background on any page, whereas Firefox required a specific visit to the settings page to do so.
This could've been a coincidence, but it's worth more debugging. I don't see this as a release blocker, because a settings page visit is necessary anyway to configure offline.
It may be that some update logic lived in the MDNWorker which yari loaded on every page: I didn't opt to port this to fred initially because things worked without it, and it would've pulled in the React user context, without doing some untangling.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing Fred's offline and settings-page service-worker behavior with the prior yari implementation in client/src/settings/mdn-worker.tsx. Reproduce updates in Blink, WebKit, and Firefox, then determine whether background updating differs by browser. Done means the cause is established and any required update behavior is verified without making this a release blocker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100