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
{{ message }}
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
Did you search for similar issues before submitting this one?
Yes
Describe the issue you encountered:
When testing #3443 it was discovered that re-locking the page exhibits counterintuitive behavior. It merely displays the unlocked status rather than re-locking.
Expected behavior:
If a user clicks on a closed lock, it should open. If a user clicks on an open lock, it should close.
Platform (Win7, 8, 10? macOS? Linux distro?):
Tested on OS X
diracdeltas
changed the title
Mixed-content lock control should be able to re-lock and reload the page like Firefox.
should be able to re-block mixed content on a page where it is unblocked
Sep 7, 2016
changing this to higher priority because currently the only way to re-blocked mixed content is by restarting the browser
bradleyrichter
changed the title
should be able to re-block mixed content on a page where it is unblocked
Mixed-content lock control should be able to re-lock and reload the page like Firefox.
Sep 7, 2016
darkdh
added a commit
to darkdh/browser-laptop
that referenced
this issue
Sep 8, 2016
2. Re-block running insecure content when frame closed
fixbrave#3770
Auditors: @diracdeltas
Test Plan:
For re-block option:
1. Go to `https://mixed-script.badssl.com/`
2. Click urlIcon and click `Load Unsafe Scripts`
3. Background should be red
4. Click urlIcon and click `Stop Loading Unsafe Scripts`
5. Background should be grey
For re-blocked on frame closed
1. Go to `https://mixed-script.badssl.com/`
2. Click urlIcon and click `Load Unsafe Scripts`
3. Background should be red
4. Close tab
5. Go to `https://mixed-script.badssl.com/` on new tab again
6. Background should be grey
Did you search for similar issues before submitting this one?
Yes
Describe the issue you encountered:
When testing #3443 it was discovered that re-locking the page exhibits counterintuitive behavior. It merely displays the unlocked status rather than re-locking.
Expected behavior:
If a user clicks on a closed lock, it should open. If a user clicks on an open lock, it should close.
Tested on OS X
0.12.0
Chrome:
Firefox:
![mixed_content_firefox](https://cloud.githubusercontent.com/assets/1434040/18287835/4fc999ee-743e-11e6-8bf3-5b358a8c5d25.gif)
Brave:
![mixed_content_brave](https://cloud.githubusercontent.com/assets/1434040/18287839/560233b6-743e-11e6-9496-58137c602623.gif)
Add an option to temporarily disable mixed content protection #3443
The text was updated successfully, but these errors were encountered: