Closed Bug 175807 Opened 22 years ago Closed 22 years ago

Typeahead can't be disabled

Categories

(Core :: DOM: UI Events & Focus Handling, enhancement, P2)

PowerPC
macOS
enhancement

Tracking

()

VERIFIED DUPLICATE of bug 176296
mozilla1.3alpha

People

(Reporter: orbplus2000, Assigned: aaronlev)

Details

Typehead on Build 2002101612 and other recent builds can't be disabled on the Mac OS X port of Mozilla. Typehead should be able to be disabled through the preferences menu or during the install process.
To keyboard nav.. we need ui for that pref, yes.
Assignee: asa → aaronl
Status: UNCONFIRMED → NEW
Component: Browser-General → Keyboard Navigation
Ever confirmed: true
OS: MacOS X → All
QA Contact: asa → sairuh
Hardware: Macintosh → All
Marlon and I were talking about doing thsi as a checkmark in the edit menu. Something like: [x] Type Ahead Find enabled or [x] Find links as you type depending on whether we want a descriptive or memorable name.
Blocks: isearch
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → mozilla1.3alpha
Bug 169490 is the typeaheadfind prefs bug.
it's actually bug 169489. :)
Some logins cause typeahead to make it impossible to enter user names and I am unable to turn it off. On the Windows and Mac Classic port I believe a custom installation allows typeahead to not be installed. The Mac OS X installation doesn't appear to provide custom install options, unless I'm somehow missing them. This bug should be reclassified as Macintosh OS X as it is not the same problem.
OS: All → MacOS X
Hardware: All → Macintosh
iirc, type ahead find is now part of the installation for all platforms. i don't think there's a way to deselect this feature in the installer now --unless it's still there in mozilla (win32/unix).
*** This bug has been marked as a duplicate of 176296 ***
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
v dup.
Status: RESOLVED → VERIFIED
No longer blocks: isearch, 169489
Component: Keyboard: Navigation → User events and focus handling
You need to log in before you can comment on or make changes to this bug.