4 ms·
I'm not sure, but I was curious too, so I submitted it for review to find out.
by npace12 3y ago
I'm not sure, but I was curious too, so I submitted it for review to find out.
- cal85 3y agoInteresting, I had assumed it wouldn't even allow uploading it if the manifest required that permission. Hope they allow it for you!
- npace12 3y agoIt got rejected today but not due to the permission, I'll pretty it up and try again. Violation reference ID: Yellow Zinc Violation: Description provided is insufficient to understand the functionality of the item.
- cal85 3y agoAppreciate you keeping me posted, please comment again when your next attempt gets approved/rejected!
- npace12 3y agoManaged to get it in! [1] I added ability to do blocking and made the "management" and "declarativeNetRequestFeedback" permissions optional, requested via a button on the popup page. While declarativeNetRequestFeedback works when you install it manually, the store version tells you the permissions are there, but chrome.declarativeNetRequest.onRuleMatchedDebug is undefined, so unfortunately, the store version can't count the number of requests. Blocking still works though, just you don't get any feedback about what's blocked. I think this is still useful to be able to block extensions, so I'll keep carrying 2 versions, 1 for the store with limited functionaly. 1: https://chrome.google.com/webstore/detail/little-rat/oiopkpalpilladnibecobcecijffaflf https://chrome.google.com/webstore/detail/little-rat/oiopkpa...