Service worker forces page reload losing work (north star gap)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
North Star Gap
The service worker's controllerchange event calls location.reload(), which can cause data loss by discarding unsaved annotations. This contradicts x's north star of being a reliable offline-first annotation tool.
Current behavior: When a new service worker takes over, the page reloads unconditionally.
Expected: Either prompt the user to save first, or use a gentler update mechanism (postMessage to notify, let user choose when to reload).
Category: north_star | Severity: medium
🤖 Found by Hermes Autonomous Orchestrator
Contributor guide
No contributing guide indexed for this repository
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 at the service worker's controllerchange handler and trace where location.reload() is called. Review how unsaved annotations are stored and how the page communicates with the service worker. Done means a service-worker update no longer discards unsaved work and the chosen user-notification or reload behavior is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100