PS:

1，Maybe it's due to a sudden crash and then reboot?

2, Or maybe it's due to the page is opened on incognito mode?

Unable to reproduce the issue on Windows 7,Mac 10.12.3 & Ubuntu-14.04 using chrome reported version-56.0.2924.87, stable-57.0.2987.110 & Canary-59.0.3044.0 as per comment#0 & 1.Observed that the words in the page ( english words and chinese text ) are not case sensitive.
Please find the attached screencast for reference & let us know if we miss anything to reproduce the issue.
Thank you!!

Deleted: 701662-Mac.mp4 1.8 MB

	701662-Mac.mp4 1.8 MB View Download

I cannot provide screencast because the site is adult and sensitive.
I thought this issue may be found its cause in source code path.
The symptom indicates Find-in-Page becomes case-sensitive, or it can also
interpreted as "un-responsive", i didn't do further check.

2017-03-17 20:23 GMT+08:00 jmukthav… via monorail <
monorail+v2.3447642152@chromium.org>:

Thank you for providing more feedback. Adding requester "jmukthavaram@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I can provide more info:

When i press Ctrl+F to show the find bar, and input some english word to
search, then i click on the "next page" link to navigate to next page, then
i press Ctrl+F again, the same find bar will echo at the same screen
location, with my previous input word.

At this time, i simply press ENTER to search again, and then i found that
search doesn't hit any result, while it should.

This problem doesn't reproduce consistently, but it happens.

2017-03-18 14:41 GMT+08:00 sheriff… via monorail <
monorail+v2.4164592774@chromium.org>:

Could you please let us know is there any latest update available on this issue by checking it on latest stable #58.0.3029.81 ? If issue is still reproducible please provide any sample webpage or test case where we can test this issue from Chrome-TE end.

Thanks!

I recently have not noticed this problem, so maybe it's fixed.
Also, turns out it's not about the case, but seems the input search item
data is lost when click to "next" page(thought it's still displayed in
input box)

2017-04-24 15:02 GMT+08:00 brajku… via monorail <
monorail+v2.2386360573@chromium.org>:

Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Closing this issue as per C#9.

ctengctsh@: If you happen to encounter the issue in future, feel free to file a new issue.