Define how localStorage is synchronized between browser tabs/windows
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9.4k
- Forks
- 3.2k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 38
Description
From https://github.com/whatwg/html/issues/335#issuecomment-156498370 and later comments it sounds like implementations of localStorage are not simply synchronous like document.cookie, but maintains an in-process cache that is synchronized with the real storage when returning to the event loop, or some similar condition.
The spec now says that "This specification does not define the interaction with other browsing contexts in a multiprocess user agent, and authors are encourages to assume that there is no locking mechanism."
If the way this is actually implemented is roughly interoperable, we should spec that. Needs thorough investigation.
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 localStorage attribute section in the HTML Standard and the linked WHATWG HTML issue 335, including the referenced comment and later discussion. Investigate how implementations synchronize localStorage across browsing contexts, then document a sufficiently interoperable specification for that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100