Find on Page doesn't work when navigating to next URL
Reported by
ale...@gmail.com,
Jan 10 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36 Steps to reproduce the problem: 1. Create two pages PageOne and PageTwo with text "foo" on both pages. 1. Visit PageOne, CMD+F > "foo" > verify that it found a match. 2. Click PageTwo link from PageOne 3. Press CMD+F which should already be filled out with the text "foo" 4. Verify that the find box shows "0 of 0" even though the text "foo" exists on page. The work around is to delete then add a character to force a modification in the find box and re-trigger find. Find should be triggered on load, not on modification. What is the expected behavior? CMD+F should report "1 of 1" or similar output since the text to be found exists on page. What went wrong? CMD+F reports text not found. Work around is to force Find to re-trigger by modifying the Find input text. Did this work before? N/A Chrome version: 55.0.2883.95 Channel: stable OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 24.0 r0
,
Jan 15 2017
My apologies, looks like there was an edge case I didn't quite get right. So the conditions are that page one should not have the text "foo" so searching it will not give a result. then click on to page two which does have the text "foo" but searching it will still show "0 of 0". Pretty much what you did in the screencast except just ensure that page one does not have "foo" but some other text
,
Jan 16 2017
Thanks for your bug report, confirmed in Chrome 55.0.2883.95, macOS 10.12.2. Looks like it has been fixed in Chrome 57.0.2979.0, though. I've attached the test files here and a screencast of both Chrome 55 and 57. Note that I press enter in order to get any "X of X" to show up. Labelling Needs-Bisect so we can work out where this was actually fixed.
,
Jan 16 2017
Issue 681165 has been merged into this issue.
,
Jan 19 2017
Thanks for the update. Was able to reproduce the issue on Mac 10.12.2,Ubuntu 14.04 and Win 10 using 55.0.2883.95 and 56.0.2924.67. Reverse bisect info: Good: 57.0.2943.0 Bad: 57.0.2942.0 You are probably looking for a change made after 436214 (known good), but no later than 436215 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/a0756df749c376d7e47b063d5e324a3a713d20df..7f875cc4451fc999c357d381d9fdd165c0a86527 kotenkov@: Could you please take a look into this if it can be merged to M56.
,
Sep 17
Archiving old bugs that have only received trivial updates for some time. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
,
Sep 24
To be honest, this issue also annoys me periodically. |
||||
►
Sign in to add a comment |
||||
Comment 1 by durga.behera@chromium.org
, Jan 13 2017Labels: M-55 Needs-Feedback
320 KB
320 KB View Download