Skip to content
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

Use "Standard" option for "Enhanced Tracking Protection" browser privacy preferences #218

Closed
arcticicestudio opened this issue Mar 20, 2020 · 0 comments · Fixed by #230
Closed

Comments

@arcticicestudio
Copy link
Owner

The Standard option for the Enhanced Tracking Protection (stats are available at about:protections) preference comes with good defaults configuration and should be used instead of the Custom option to also prevent sites from breaking due to cookie blocking.

@arcticicestudio arcticicestudio added this to the 0.1.0 milestone Mar 20, 2020
@arcticicestudio arcticicestudio self-assigned this Mar 20, 2020
arcticicestudio added a commit that referenced this issue Mar 23, 2020
The "Standard" option for the "Enhanced Tracking Protection" [1] (stats
are available at `about:protections`) preference comes with good
default configurations and is now used instead of the "Custom" option to
also prevent sites from breaking due to cookie blocking.

[1]: https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-preview

GH-218
arcticicestudio added a commit that referenced this issue Mar 24, 2020
#230)

The "Standard" option for the "Enhanced Tracking Protection" [1] (stats
are available at `about:protections`) preference comes with good
default configurations and is now used instead of the "Custom" option to
also prevent sites from breaking due to cookie blocking.

[1]: https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-preview

Closes GH-218
@arcticicestudio arcticicestudio removed their assignment Mar 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant