How are unloaded tabs represented?
Open
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
Mobile browsers put tabs into an "asleep" state to save memory & battery as needed. If you focus the tab later, the page is reloaded, but may regain some state within form elements.
This behaviour is completely unspecified, but I think we should put some guidance in the SW spec for these pages.
Specifically:
- Do asleep tabs prevent a SW moving from "waiting" to "active"?
- Do asleep tabs show up in
clients.getAll()?
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 reading the Service Worker specification sections covering the waiting-to-active transition and clients.getAll(), then investigate how asleep mobile tabs are treated. Done means the specification provides clear guidance for both questions raised in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100