-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
The segment is blocked but ads history indicates that it is not #17672
Labels
bug
feature/ads
OS/Desktop
priority/P2
A bad problem. We might uplift this to the next planned release.
QA Pass-Linux
QA/Test-Plan-Specified
QA/Yes
release-notes/exclude
Milestone
Comments
24 tasks
Verification passed on
Verified ads are blocked:
Verified able to unblock and indicator is updated: Verified ads are shown after unblocking:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
feature/ads
OS/Desktop
priority/P2
A bad problem. We might uplift this to the next planned release.
QA Pass-Linux
QA/Test-Plan-Specified
QA/Yes
release-notes/exclude
After user blocks a segment in ads history, it may happen that the indicator will be reset. User may think that the segment is not blocked when in fact it is blocked.
Steps to Reproduce
notification ad - blocked untargeted segment v8.txt
30-day history
30-day history
Note: also noticed that this happens when certain amount of time passes but could find exactly how long is needed
Actual result:
The segment is blocked but ads history indicates that it is not

Note: UI change is permanent, not fixed after browser restart
Expected result:
The segment is blocked but ads history indicates that it is indeed blocked
Reproduces how often:
Easily reproduced
Brave version (brave://version info)
cc @tmancey @moritzhaller @jsecretan @rebron @brave/legacy_qa
The text was updated successfully, but these errors were encountered: