Closed
Bug 179549
Opened 22 years ago
Closed 20 years ago
typeaheadfind searches for wrong string if the middle does not match
Categories
(SeaMonkey :: Search, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jmd, Assigned: aaronlev)
Details
Load http://news.google.com/help/about_news_search.html hit "/250" quickly to search the text for "250" See type ahead find scroll all the way to the bottom and highlight the "20" in "2002" The 5 is overwritten as soon as it's entered, as it does not match, even though it's obvious I want "250" since it was all typed together. This is unpredicable behavior, and causes me to lose where ever I was at in the document and show me incorrect information.
Comment 2•22 years ago
|
||
I'm not sure if this is a valid bug. In fact, there's nothing about typing fast. You get the same result if you type "/250" really slowly. If you look at the statusbar, you will see the following feedback text: type statusbar ------------------- /2 text found "2" /25 text not found "25" (you also hear a beep) /250 text found "20" So my understanding is: if a text is found, it goes to that place. If you continue typing, it continues to try to match the text. If nothing is matched, a beep signals the error, but keeps the previous string. If you continue typing after that error, the "error-typing" is simply ignored. It's as if you typed backspace. Question: feature or bug?
Assignee | ||
Comment 3•20 years ago
|
||
More often than not I this does what I want. I haven't heard any major complaints in a year. No DUP's. No votes.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
Updated•16 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•