-
-
Notifications
You must be signed in to change notification settings - Fork 387
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
Disable on localhosts #2666
base: master
Are you sure you want to change the base?
Disable on localhosts #2666
Conversation
I think it would be better to take the tack discussed in #817 (comment) and disable learning on local domains. This means Privacy Badger will still be enabled and will report domains, do widget replacement, etc.. We just don't want to ever get local domains in |
So that's for when the site you are on is a local host domain. What about when local host domains are included as resources on a site?
Edit: We currently completely ignore local host domains when it comes to modifying/blocking their requests and reporting them in the UI. I don't think we have a similar check on the learning side, however. |
Ah, this makes sense! I'll go this route, then. Next commit will go this direction 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are other learning code paths: review the places incognito.learningEnabled()
gets called.
Now that #2679 was merged, this should be rebased on master. |
ba2b685
to
c987989
Compare
This fixes #817
Instead of disabling pb entirely on localhosts, this now just removes learning capabilities when the tab origin is from a predictable localhost address.