This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 977
Blocking rules are not limited to private tabs #10829
Labels
Milestone
Comments
In general, site settings that are changed in a private tab should be written to so settings changed in private tabs should not affect regular tabs. |
ok, so this is a regression then. Will look into it |
this bug was introduced with #10289, problem is that when we cache bravery settings but we don't add private flag |
NejcZdovc
added a commit
to NejcZdovc/browser-laptop
that referenced
this issue
Sep 7, 2017
Resolves brave#10829 Auditors: Test Plan:
8 tasks
diracdeltas
added a commit
that referenced
this issue
Sep 7, 2017
Fixes cache problem with private tabs for siteSettings
diracdeltas
added a commit
that referenced
this issue
Sep 7, 2017
Fixes cache problem with private tabs for siteSettings
diracdeltas
added a commit
that referenced
this issue
Sep 7, 2017
Fixes cache problem with private tabs for siteSettings
diracdeltas
added a commit
that referenced
this issue
Sep 7, 2017
Fixes cache problem with private tabs for siteSettings
This was referenced Sep 14, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Test plan
#10836 (comment)
Describe the issue you encountered:
So what is happening here is that you set ad blocking rule in private tab and this rule is applied outside private tab as well.
Is this something that is intended? cc @diracdeltas
The text was updated successfully, but these errors were encountered: