-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Minimum visits for publisher relevancy setting not being respected #2110
Labels
blocked
feature/rewards
priority/P2
A bad problem. We might uplift this to the next planned release.
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Test-Plan-Specified
QA/Yes
release-notes/include
Milestone
Comments
18 tasks
NejcZdovc
added a commit
to brave/brave-core
that referenced
this issue
Jan 21, 2019
NejcZdovc
added a commit
to brave/brave-core
that referenced
this issue
Jan 26, 2019
Still reproducible
|
@btlechowski was not added yet |
Verification passed on
Used test plan from brave/brave-core#1399 Verification passed on
Verified passed with
|
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
blocked
feature/rewards
priority/P2
A bad problem. We might uplift this to the next planned release.
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Test-Plan-Specified
QA/Yes
release-notes/include
Description
If I change the 'Minimum visits for publisher relevancy' setting from default (1 visit) to something else (5 or 10 visits), sites get added to the table after 1 visit and show 0%.
Steps to Reproduce
Actual result:
Site is added to table with 0% attention. If you continue to visit the site until the number of visits is reached, the site % does not adjust, it stays at 0%.
Expected result:
Setting should be respected. Site should not be added until number of visits is achieved.
Reproduces how often:
easily
Brave version (brave://version info)
Reproducible on current release:
Website problems only:
Additional Information
cc @brave/legacy_qa to check on other platforms
The text was updated successfully, but these errors were encountered: