Skip to content

/ brave-browser

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

Jump to bottom

Disabling global HTTPS Everywhere setting does not disable HTTPSEverywhere #3424

Open
jumde opened this issue Feb 20, 2019 · 1 comment
Open

Disabling global HTTPS Everywhere setting does not disable HTTPSEverywhere #3424

jumde opened this issue Feb 20, 2019 · 1 comment
Labels
feature/global-settings feature/https-everywhere priority/P3
Projects
General

Comments

@jumde
Copy link
Contributor

@jumde jumde commented Feb 20, 2019

Description

Global HTTPS Everywhere switch should disable HTTPS upgrades even if the per-site switch is enabled.

Steps to Reproduce

  1. Navigate to brave://setttings and disable HTTPS Everywhere
  2. Open twitter.com and check the stats on brave://newtab
  3. The count increases

Actual result:

Global switch does not disable HTTPSEverywhere

Expected result:

HTTPSEverywhere should be disabled

Reproduces how often:

Easily

Brave version (brave://version info)

0.63.0 Chromium: 73.0.3683.39 (Developer Build) (64-bit)
@tomlowenthal
Copy link
Member

@tomlowenthal tomlowenthal commented Feb 20, 2019

Do the other global Shields settings work as intended?
@jumde jumde mentioned this issue Feb 20, 2019
Merged
9 of 18 tasks complete
@rebron rebron added this to Untriaged Backlog in General Feb 26, 2019
@rebron rebron moved this from Untriaged Backlog to P3 & P4 Backlog in General Mar 5, 2019
@rebron rebron moved this from P4 Backlog to P3 Backlog in General Mar 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature/global-settings feature/https-everywhere priority/P3
Projects
General
  
P3 Backlog
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
@fmarier @tomlowenthal @jumde @bsclifton @rebron
You can’t perform that action at this time.