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] "Find in page" incorrectly starts from '5/16' instead of '1/16' when the page is at the top #5636

Open
SuYanqi opened this issue Feb 11, 2025 · 5 comments

Comments

@SuYanqi
Copy link

SuYanqi commented Feb 11, 2025

Describe the bug

The search results display '5/16

Screen.Recording.mov

' as the initial match.

How to Reproduce

  1. Open the page you want to search, e.g., www.wikipedia.org.
  2. Tap the 'three-dot' menu button.
  3. Tap 'Find in page' button.
  4. Enter your search term or phrase in the search bar, e.g., 'h'.

Expected behavior

The search results should display '1/16' as the initial match, especially since the page is at the top without any scrolling.

Environment

- DDG App Version: 5.225.0 (52250000)
- Device: Galaxy S21 5G
- OS:Android 12
Copy link
Contributor

Thank you for opening an Issue in our Repository.
The issue has been forwarded to the team and we'll follow up as soon as we have time to investigate.
As stated in our Contribution Guidelines, requests for feedback should be addressed via the Feedback section in the Android app.

@subhasha1
Copy link

@SuYanqi

This seems to be caused by Android's native WebView implementation. I was able to reproduce this with my chrome browser.

During my investigation, I noticed that FindListener.onFindResultReceived call was made from android.webkit.WebView with incorrect activeMatchOrdinal, which was the cause of this bug.

I think it would be good idea to report on Google's issue tracker, perhaps.

@SuYanqi
Copy link
Author

SuYanqi commented Feb 28, 2025

@SuYanqi

This seems to be caused by Android's native WebView implementation. I was able to reproduce this with my chrome browser.

During my investigation, I noticed that FindListener.onFindResultReceived call was made from android.webkit.WebView with incorrect activeMatchOrdinal, which was the cause of this bug.

I think it would be good idea to report on Google's issue tracker, perhaps.

Hi @subhasha1,

That’s very interesting!

I’ll report this issue on Google’s issue tracker.

Would you be okay with me CC’ing your GitHub email in the report?

@subhasha1
Copy link

@SuYanqi

Would you be okay with me CC’ing your GitHub email in the report?

Yes thats fine! :)

@SuYanqi
Copy link
Author

SuYanqi commented Mar 3, 2025

@SuYanqi

Would you be okay with me CC’ing your GitHub email in the report?

Yes thats fine! :)

Hi @subhasha1

I found that I don’t have access to CC you, so I mentioned your email in the issue instead.

Here’s the issue link: https://issuetracker.google.com/issues/400119366. Feel free to join the discussion if you're interested.

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