178743 - confusing status bar feedback when typeaheadfind fails to find something

Status: REOPENED

(Core :: DOM: UI Events & Focus Handling, defect)

Description

[Jesse Ruderman]

Steps to reproduce:
1. Go to http://www.webmasterworld.com/.
2. Type "phoenix".  (Note that the word "phoenix" does not appear on the page.)

Result:
a) "ph" finds a link containing the word "PHP".
b) "pho" says "link not found: pho".
c) "phoe" says "link not found: phe".

If I stop typing at this point (usually because I noticed the beep after b), I
wonder: did I mistype "phoe" as "pheo" or "phe" or "phie", or was the text I
meant to type really not found?  The answer is usually the latter, but I can't
tell that by looking at the status bar text, so I often try again from the
beginning.

d) "phoen" says "link not found: phn".
e) "phoeni" says "Type ahead find stopped".

First, why suddenly stop after 4 missed characters?

Second, the text "type ahead find stopped" is inaccurate in this case, because
pressing backspace continues searching at "ph", and typing "phoe" again does not
start a new search.  "Type ahead find stopped" usually means that it has stopped
completely and reset.

Comment 1

[Aaron Leventhal]

*** This bug has been marked as a duplicate of 176037 ***

Comment 2

[Jesse Ruderman]

Only the first part of this bug was fixed in bug 176037.  The "Type ahead find
stopped" thing still happens.  Akkana also mentioned this in bug 176037 comment 2.

Comment 3

[David Bolter [:davidb] (NeedInfo me for attention)]

Mass un-assigning bugs assigned to Aaron.