Inconsistency: storage onChanged
Open
Nobody has claimed this yet.
implemented: chrome
implemented: safari
supportive: firefox
topic: storage
- Dominant language
- Bikeshed
- Stars
- 711
- Forks
- 95
- Avg merge
- 10d 11h
- Merged PRs (30d)
- 2
Description
Inconsistency: storage onChanged
I have comes across an inconsistency in the return of the storage onChanged event.
(I am not aware of the return from other browsers.)
Example:
// same for browser and chrome APIs
browser.storage.onChanged.addListener()
browser.storage.sync.onChanged.addListener()
Firefox
- Returns all values, changed or not
- Event is dispatched regardless of the changed values
Chrome
- Chrome returns only the changed values
- Event is not dispatched if there are no changed values
See also:
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 issue 511 and the linked Bug 1833153, then compare the documented Firefox and Chrome behavior for storage.onChanged. Determine the expected event and returned-value behavior from the issue discussion; done means the inconsistency has an agreed resolution recorded for the WebExtensions specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100