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
When changing from aggressive to standard (or vice versa), we use the cached values of the previous setting resulting in no change in behaviour in some cases when switching settings
NOTE: This issue will mess with the behaviour in the STR so make sure it is merged first #37084
Switch modes (i.e. from standard to aggressive or aggressive to standard)
Reload the page (note: you have to click on the url bar and enter the address or else you are refreshing the interstitial page and no change will occur)
Actual result:
No change of behaviour between standard and aggressive mode
Expected result:
Change of behaviour between standard and aggressive mode
Reproduces how often: [Easily reproduced, Intermittent Issue]
Brave Version:
Can you reproduce this issue with the most recent build from TestFlight?
Can you reproduce this issue with the previous version of the current build from TestFlight?
Can you reproduce this issue with the current build from AppStore?
Device details:
Website problems only:
Does the issue resolve itself when disabling Brave Shields?
Is the issue reproducible on the latest version of Mobile Safari?
Additional Information
The text was updated successfully, but these errors were encountered:
Description:
When changing from aggressive to standard (or vice versa), we use the cached values of the previous setting resulting in no change in behaviour in some cases when switching settings
NOTE: This issue will mess with the behaviour in the STR so make sure it is merged first #37084
Steps to Reproduce
Actual result:
No change of behaviour between standard and aggressive mode
Expected result:
Change of behaviour between standard and aggressive mode
Reproduces how often: [Easily reproduced, Intermittent Issue]
Brave Version:
Device details:
Website problems only:
Additional Information
The text was updated successfully, but these errors were encountered: