Closed Bug 172283 Opened 22 years ago Closed 22 years ago

No autostart for typeaheadfind in browser, or at least a pref

Categories

(SeaMonkey :: Find In Page, enhancement)

Product:
SeaMonkey
Component:
Find In Page
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 176296

People

(Reporter: bugzillas+padREMOVETHISdu, Assigned: aaronlev)

References

Details

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 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
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.
Status: VERIFIED → UNCONFIRMED
Resolution: DUPLICATE → ---
Summary: Typeaheadfind annoys if a char. is mistakenly hit → RFE: no autostart for typeaheadfind in browser, or at least a pref
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
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: RFE: no autostart for typeaheadfind in browser, or at least a pref → No autostart for typeaheadfind in browser, or at least a pref

*** This bug has been marked as a duplicate of 176296 ***
Status: NEW → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → DUPLICATE
Blocks: isearch
v
Status: RESOLVED → VERIFIED
Component: Keyboard: Navigation → Keyboard: Find as you Type
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.