You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that CNAME-uncloaking has become more common, I think it's time to expose the setting in the user interface and make it easier for users to opt-out if needed, considering that it may causes undue delay in page loading when a proxy is used, as reported in this bugzilla issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1694404.
The setting should be rendered as disabled in browsers not supporting the API for allowing CNAME-uncloaking.
The text was updated successfully, but these errors were encountered:
gorhill
changed the title
Expose CNAME-uncloaking as an Privacy option in the Settings pane
Expose CNAME-uncloaking as a Privacy option in the Settings pane
Mar 1, 2021
Related issue:
- uBlockOrigin/uBlock-issues#1513
Prior to this commit, the ability to enable/disable the
uncloaking of canonical names was only available to advanced
users. This commit make it so that the setting can be
toggled from the _Settings_ pane.
The setting is enabled by default. The documentation should
be clear that the setting should not be disabled unless it
actually solves serious network issues, for example:
https://bugzilla.mozilla.org/show_bug.cgi?id=1694404
Also, as a result, the advanced setting `cnameUncloak` is no
longer available from within the advanced settings editor.
Now that CNAME-uncloaking has become more common, I think it's time to expose the setting in the user interface and make it easier for users to opt-out if needed, considering that it may causes undue delay in page loading when a proxy is used, as reported in this bugzilla issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1694404.
The setting should be rendered as disabled in browsers not supporting the API for allowing CNAME-uncloaking.
The text was updated successfully, but these errors were encountered: