Typeaheadfind is a truly helpful way of incremental search. But as of now it suffers from a drawback. Typeaheadfind as of now violates the norm of using only keys other than alphanumeric keys like control+ / alt+ combinations / func. keys / arrow keys to perform tasks other than inserting characters. Example: If a user thinks the location bar has been selected & types a URL when in fact it wasn't selected. typeahead search will annoy him. Possible Soln.: Edit->Preferences->Typeahead can give options: ( ) typeaheadfind enabled by default ________________ (*) key to enable typeahead |Accel+T | |________________| where thwe default could be the first, but people like me can choose the second.

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

v

This is not a dup. Bug 158752 is for menu items and accelerators so that typeaheadfind can be used in Mailnews and Composer, where automatic start with conflict with other important keystrokes. In bug 158752, we might add the menu items to browser as well, but it would still start automatically. This bug is about being able to turn off autostart in the browser, and requiring a prefix keystroke to start it, in all places typeaheadfind is used.

Possibly incremental search can be shifted to the find dialog box (as you type in the find dialog, typeaheadfind occurs in the main window). In that case one need not bother about proliferation of menus, or of preferences, etc. which were bugging bug#158752

confirming bug

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

v