Allow the service worker to work in the background without stopping for installed PWA
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
Current situation:
as soon as the page is closed or becomes inactive, the browser stops the work of the service worker. The idea is clear - the browser cannot keep all service workers of all pages ever opened in working state.
But not so long ago, we had the opportunity to install PWA applications (or add them to the home screen in iOS)!
This action transfers a simple page with service worker to the category of installed applications.
Native installed applications have the privilege to stay running in the background.
Why do the installed PWA applications not have this feature!?
Proposal:
to allow the installed PWA applications to have service worker running in the background without stopping until they are uninstalled.
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 examining the Service Worker lifecycle rules and how installed PWA applications are distinguished from ordinary pages. The issue names no files or tests; completion would require an agreed specification change defining background execution until an installed PWA is uninstalled.
Written by the indexing model from the issue text.
Assessment
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100