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
The intention of Brave Today's scoring of items was to consider the last 2 weeks of history items. However, without specifying a maxResults in the chrome.history.search API call, we are limited to 100 items. We should specify a maxResults of 2000 items.
I'd say the testing / QA of this isn't really neccessary because it's obvious what the call is doing from the code, and manual testing would be very annoying and prone to false negatives:
Fresh profile
Visit the second item in the Brave Today feed, as long as it's not the same publisher source as the first item.
Visit 101 more sites.
Generate a new Brave Today feed by disabling a publisher source that is not the first or second item.
--> Observe that the item which was 2nd is now 1st.
The text was updated successfully, but these errors were encountered:
petemill
changed the title
Brave Today history scoring is limited to 100 items
Brave Today history scoring should not be limited to 100 items
Dec 8, 2020
The intention of Brave Today's scoring of items was to consider the last 2 weeks of history items. However, without specifying a
maxResults
in thechrome.history.search
API call, we are limited to 100 items. We should specify amaxResults
of2000
items.I'd say the testing / QA of this isn't really neccessary because it's obvious what the call is doing from the code, and manual testing would be very annoying and prone to false negatives:
--> Observe that the item which was 2nd is now 1st.
The text was updated successfully, but these errors were encountered: