Skip to content
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

Load new content button doesn't appear to work, and remains after click #26265

Closed
stephendonner opened this issue Oct 26, 2022 · 1 comment
Closed

Comments

@stephendonner
Copy link

Description

Load new content button doesn't appear to work, and remains after click

This is pretty similar to #20409, but that's on Android

Steps to Reproduce

  1. install 1.47.14
  2. launch Brave
  3. open brave://flags
  4. set brave://flags/#brave-news-v2 to Enabled
  5. click Relaunch
  6. open a new-tab page
  7. click Customize
  8. click Turn on Brave News
  9. click on Follow on the Brave channel
  10. click to Unfollow the Top Sources category/channel
  11. dismiss the dialog
  12. wait
  13. when it appears, click on Load new content
  14. nothing (seemingly) happens

Actual result:

Nothing seems to happen, and the Load new content button doesn't dismiss, either

Expected result:

It should at least dismiss, if it can't find new content

Reproduces how often:

100%

Brave version (brave://version info)

Brave 1.47.14 Chromium: 107.0.5304.62 (Official Build) nightly (x86_64)
Revision 1eec40d3a5764881c92085aaee66d25075c159aa-refs/branch-heads/5304@{#942}
OS macOS Version 11.7.1 (Build 20G918)

Version/Channel Information:

  • Can you reproduce this issue with the current release?
  • Can you reproduce this issue with the beta channel?
  • Can you reproduce this issue with the nightly channel?

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields?
  • Does the issue resolve itself when disabling Brave Rewards?
  • Is the issue reproducible on the latest version of Chrome?

Miscellaneous Information:

cc @mattmcalister @rebron @fallaciousreasoning @petemill @srirambv

@fallaciousreasoning
Copy link

I think this should be fixed now the backend has been updated. I just tested and couldn't reproduce.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants