Unable to disable the `Scripts blocked` after upgrade to 0.68.133
See original GitHub issueDescription
Unable to disable the Scripts blocked
after upgrade to 0.68.33
Steps to Reproduce
- Clean profile 0.68.132
- Open https://brianbondy.com/
- Open BR panel and enable the scripts for https://brianbondy.com/
- Upgrade to 0.68.133
- Try disabling the
Scripts blocked
switch after upgrade - Unable to disable the
Scripts blocked
after upgrade to 0.68.33
Actual result:
Expected result:
Should be able to disable the Scripts blocked
after upgrade to 0.68.33
Reproduces how often:
Always
Brave version (brave://version info)
Brave | 0.68.133 Chromium: 77.0.3865.65 (Official Build) (64-bit) |
---|---|
Revision | 87a331a3169cab563505fb44011058b904011ba1-refs/branch-heads/3865@{#726} |
OS | Windows 10 OS Version 1803 (Build 17134.523) |
Version/Channel Information:
- Can you reproduce this issue with the current release? No
- Can you reproduce this issue with the beta channel? Yes
- Can you reproduce this issue with the dev channel? Yes
- Can you reproduce this issue with the nightly channel? Yes
Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? NA
- Does the issue resolve itself when disabling Brave Rewards? NA
- Is the issue reproducible on the latest version of Chrome? NA
Miscellaneous Information:
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Manual test run on OS X for 0.68.x - Release Hotfix 2 #6028
(#5952) Unable to disable the Scripts blocked after upgrade to 0.68.133.(#5973) One-time tip data reset to Zero after...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Found a scenario that occurs on a clean profile with 0.68.133:
For comparison, here’s how this works on 0.68.132:
Reproduced on macOS using STR from description when updating from
0.68.132
to0.68.133
Note - close and restart of Brave did not resolve this.
Additionally, could not reproduce when updating from
0.68.131
to0.68.132
.