You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I began working on a Google Chrome port of the extension in the chrome branch, but quickly hit a wall due to limitations in how much the chrome.storage.local API is allowed to store for an extension. Everything else seems to work, except for storing 16MB+ Bloom filters (which raises exceptions).
Note that in this port, I still request the unlimitedStorage permission in the manifest.json file, but Chrome doesn't seem to be respecting it.
I am opening this issue as a place for discussion about how to overcome these storage limitations so that the extension can be ported to Chrome with as few changes as possible.
The text was updated successfully, but these errors were encountered:
I began working on a Google Chrome port of the extension in the
chrome
branch, but quickly hit a wall due to limitations in how much thechrome.storage.local
API is allowed to store for an extension. Everything else seems to work, except for storing 16MB+ Bloom filters (which raises exceptions).Note that in this port, I still request the
unlimitedStorage
permission in themanifest.json
file, but Chrome doesn't seem to be respecting it.hackernews-button/manifest.json
Line 27 in a479e73
For reference on why
unlimitedStorage
might not be working in Chrome, see the following references:I am opening this issue as a place for discussion about how to overcome these storage limitations so that the extension can be ported to Chrome with as few changes as possible.
The text was updated successfully, but these errors were encountered: