I was looking at the graph of Firefox users of the extension. About a third of Firefox users are still using 0.5.5. I believe that it is due to 0.6 needs "browsingData" permissions. However, the permission is only needed for blocking FPD. As this is only opt-in and we plan it to stay opt-in for AFPS, it would make sense to me to make the permission optional, see https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/optional_permissions (AFAIU "browsingData" are not cross-browser compatible but can be used optionally).
Can you have a look to make the permissions optional (possibly also have a look at Chrome permission). Please document instructions for adding an optional permission as we might add optional permissions in the future.
Worked on it in 6855163. BrowsingData is set to optional in FF. Chromium doesn't support it yet, but still added to optional permissions in chrome's manifest. For now, Chrome takes BrowsingData as a normal permission, but if future Chrome release will add support for it, it will be automatically optional for JShelter (logic is already there).
Furthermore, I'm planning to add support for alternative cleaning solution to supplement the current one and also work as a fallback in case a user refuses BrowsingData permissions.
Metadata Update from @polcak: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @polcak: - Issue untagged with: question
It worked and 0.5.x users are finally migrating to a new version:
<img alt="screenshot.png" src="/JShelter/webextension/issue/raw/files/369506c880ff40f2341f7f52127ce809f2b654ed5e01929a54f10d0124e7048c-screenshot.png" />
Login to comment on this ticket.