Repository navigation
Chrome Web Store doesn't like Tabs permissions #465
Description
The Google Web Store doesn't allow Tabs permissions used by the service_worker.js file.
Information provided from Google when trying to deploy Google extension to the Google Web Store.
Violation(s):
Use of Permissions:
Violation reference ID: Purple Potassium
Violation:
The following permission(s) need not be requested for the methods/properties implemented by the item:
tabs
How to rectify: Remove the above permission(s). The properties used by the items will continue to function even without requesting these permissions.
Relevant section of the program
policy:
Request access to the narrowest permissions necessary to implement your Product's features or services. Don't attempt to "future proof" your Product by requesting a permission that might benefit services or features that have not yet been implemented. (learn more)
This violation was detected as a result of an internal review. Learn more about enforcement here.
For reference: https://developer.chrome.com/docs/webstore/troubleshooting/#excessive-permissions
Activity
eoftedal commentedon Apr 9, 2025
What do you mean by "deploy Google extension to the Google Web Store"?
eoftedal commentedon Apr 9, 2025
If you are referring to this https://chromewebstore.google.com/detail/retirejs/moibopkbhjceeedibkbkbchbjnkadmom it's not an official extension managed here.
anthnyajp commentedon Apr 9, 2025
No, you stated that you were looking for someone create a new chrome extension where the code is managed here. I uploaded it to the Google web store to see what it came back with after review and it was denied because of the tabs permissions. The service_worker.js file uses tabs, so it'll need to be re-written. I'm trying some things but still working through some errors.
eoftedal commentedon Apr 10, 2025
Ok, I understand. What I was trying to do was to get control over the (now defunct) chrome extension, as it's unofficial and still using the logo etc. of the tool. I didn't originally want the extension to be in the web store, but given it's there, it should be controlled from this repo to avoid someone abusing the trust of this tool.
eoftedal commentedon Apr 17, 2025
Thanks for looking into this btw, @anthnyajp