-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Permission Explanation #34
Comments
The extension currently relies on Chrome Extension's The use of |
I just added this into FAQ. Thanks for reporting your concerns. I'll try to find a better solution for this. |
I checked the way Octotree handles this problem. It tries to inject content scripts into every webpage and if it got an error (because of no permission granted for most sites) it stops. Octotree won't know the exact URL you are visiting but if no error occurs it knows that the site's permission is already granted. GitHub Hovercard tries to make sure the site you are visiting is already in the granted list before it injects content scripts by using the |
@Justineo sounds like a huge oversight from Chromium IMHO. They should've implemented a method to check if you have permission on the current site. |
You can now remove that permission by using 2 modules I wrote recently: https://github.com/fregante/webext-domain-permission-toggle You'd just need these and some adjustments to manifest.json npm i webext-domain-permission-toggle webext-dynamic-content-scripts // in background.js
import 'webext-dynamic-content-scripts';
import addDomainPermissionToggle from 'webext-domain-permission-toggle';
addDomainPermissionToggle(); |
It'd be really nice to know why this plugin needs the permissions it requests, especially why it needs to view my browser history.
I can't think of any reason why it would need the history, so at this point this makes the plugin quite untrustworthy TBH.
The text was updated successfully, but these errors were encountered: