Closed Bug 1447459 Opened 7 years ago Closed 7 years ago

Find in page (longer than 2 letters) just now began failing 100%

Categories

(Toolkit :: Find Toolbar, defect)

Product:
Toolkit
Component:
Find Toolbar
Version:
59 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1414693

People

(Reporter: loren, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0 Build ID: 20180315233128 Steps to reproduce: I had about six tabs open, some academic papers, some popular press. A Find in page search was open in one pop site with several occurrences highlighted. (The computer had been in hibernation since that tab and search was opened...) I opened a new academic site from Google search and tried to do a Find - it failed on any second letter, despite obvious occurrences. Actual results: I went back through other tabs, and all failed to Find obvious occurrences. Often on the first letter. When I got to the open search it still showed its successful results, but as soon as I edited the search term it totally failed as well. I tried new tabs, quit Firefox and restarted it, a complete restart of Windows with no other apps open. Find in page is now 100% broken. Expected results: Since a recent Firefox update, I've also noticed it getting into a state where it can't update the screen when I try to close a tab, but is otherwise apparently working. If I switch to another app and back everything I've tried to close is closed. No clue how that could be related... My main goal here is what can I check to debug this Find problem further? This is not really a "tablet", but it is a Surface Book with Windows 10 Creators and touch capability - and screen scaling. It seems to trigger many bugs a normal computer wouldn't... Also, I've changed the highlight colors used by Find - but that caused no problems for many months. Can't imagine it triggered today's fail.
OK, I'm just playing with this here. Turns out it can find single letters, if they are bounded by spaces or apostrophes. If no single instances exist on the page, it fails on the first search letter you type. It can also find two-letter words, if any exist. On this page or any page. Beyond two letters, everything fails. That must provide someone who knows the code with a clue where I can look next...
Summary: Find in page just now began failing 100% → Find in page (longer than 2 letters) just now began failing 100%
Component: Untriaged → Find Toolbar
Product: Firefox → Toolkit
Still at this. I've now discovered that there is no visible indication whatsoever whether Match Case and Whole Words are on or off. If I turn on Whole Words, I can duplicate most of the symptoms I was seeing above. If I turn it off it finds any length words as expected in current tests. I could swear I tried fully matching three-letter words and saw them fail in my earlier tests. But maybe they did not Match Case...??? I'm pretty sure I typed them exactly like visible instances... I have never intentionally turned on Match Case and Whole Words until now. Somehow they turned themselves on overnight, and propagated to each new tab. HOW CAN IT BE THERE IS NO VISIBLE INDICATION THEY HAVE BEEN TURNED ON ??? !!!
so, this is duplication of bug 1414693
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.