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

[BUG]: First Click on Graph Scrolls Page to Top #17276

Open
3 of 4 tasks
brishtibheja opened this issue Oct 17, 2024 · 1 comment
Open
3 of 4 tasks

[BUG]: First Click on Graph Scrolls Page to Top #17276

brishtibheja opened this issue Oct 17, 2024 · 1 comment

Comments

@brishtibheja
Copy link

Checked for duplicates?

  • This issue is not a duplicate

Does it also happen in the desktop version?

  • This bug does not occur in the latest version of Anki Desktop

What are the steps to reproduce this bug?

  1. Go to Statistics.
  2. Go to the bottom at Added graph.
  3. Click on a bar on the right side of the graph.

Expected behaviour

The page scrolls to just above the graph. The next click works completely fine.

Debug info

2.19beta6

(Optional) Anything else you want to share?

This issue existed back when the new statistics was added. It was reported here: #15805

The fix was working fine until recently. On another device, I can't reproduce this using beta5 so it's probably beta6 that introduced this.

Research

  • I have checked the manual and the FAQ and could not find a solution to my issue
  • (Optional) I have confirmed the issue is not resolved in the latest alpha release (instructions)
@deysak
Copy link
Contributor

deysak commented Oct 17, 2024

The bug resurfaced after #17250 (which used a custom WebView implementation to handle nested scroll for Statistics),
and was gone after #16027 (which used NestedScrollView to handle nested scroll for Statistics),
before which the same bug existed.

The custom WebView implementation does not appears to be the root cause of the bug, as using the vanilla WebView also results in the same bug.

Somehow NestedScrollView unintentionally suppressed the cause,

likely because how it treats the incoming WebView:

Image

Which is in contrast to native/custom WebView:

Image

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