-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Document reason for "Access your data for all websites" browser permission (more prominently?) #7314
Comments
RGH's own code doesn't have any permission requests, adding permissions is only possible via:
In your case, you most likely clicked Chrome's native UI toggle because we never ask for "all" @busches The problem is most likely related to extraneous CSS injection |
I'm on Firefox, though, not Chrome |
s/Chrome/Firefox/ same |
It keeps sending |
I observed the same and I had the permission OP reported already off. Additionally, if I right click the icon in the menu bar, "Enable for this domain" is unchecked for the sites I was inadvertently spamming... |
Literally impossible. Refined GitHub does not have any more permissions than what you give. Permissions are handled and limited by the browser.
That checkbox doesn't work well when the "all sites" permission was granted |
Apparently this is to identify whether a server is GitHub Enterprise or not? Anyways, one other thing worth noting: when using the "Start process to identify feature..." button under the add-on's preferences, and the "all sites" permission is granted, it can cause the feature identification UI to appear on other sites, such as the GCC bugzilla, which can look really weird when the site in question isn't designed for it. |
Duplicate of #7319 (comment) |
In hands entrusted, a tool I gave, In your grip, it's you who's harmed, |
While trying to figure out why RefinedGithub was causing me some issues on a non-GitHub website (
gcc.gnu.org
to be specific), I noticed that RefinedGithub has "Access your data for all websites" under "Optional permissions for added functionality" enabled on my browser. I may very well have enabled that permission myself at some point, but if so, I forget why. If there was some sort of prompt or dialog that showed up explaining why the extension wanted the permission, then I've forgotten what it might have said. If documentation for why the extension might want this browser permission is already available, it should be made more prominent, and linked to from (more of) the places in which a user might look for documentation.The text was updated successfully, but these errors were encountered: