If Use Find as you type in options is off only userpref accessibility.typeaheadfind is set to false userpref accessibility.typeaheadfind.autostart is left default (=true) For people using chats and fora it's extremely annoying if you use ' or / and the autostart starts the find toolbar and moves focus to that input. expected: if accessibility.typeaheadfind is set false accessibility.typeaheadfind.autostart should respect that and regarless of its value not autostart (respect accessibility.typeaheadfind false).
This bug is fixed with the patch in bug 251073
Depends on: 251073
OS: Windows 2000 → All
Hardware: PC → All
Summary: Options , Find as you type = off , should respect typeaheadfind and not allow autostart → Find as you type = off pref, should respect typeaheadfind and not allow autostart
*** Bug 264814 has been marked as a duplicate of this bug. ***
No longer depends on: 251073
(In reply to comment #1) > This bug is fixed with the patch in bug 251073 so typing a / or a ' on a page (not in an input) causing the findbar to popup is designed behaviour ? I though this would be disabled, only leaving you the option to press F3 to activate it ?
(In reply to comment #3) > (In reply to comment #1) > > This bug is fixed with the patch in bug 251073 > > so typing a / or a ' on a page (not in an input) causing the findbar to popup is > designed behaviour ? > I though this would be disabled, only leaving you the option to press F3 to > activate it ? The final patch to fic bug 251073 was not that patch that included the fix for this bug. I am working on a new patch to fix the remainder of the preference issues including this one.
this bug is fixed with the patch in bug 265915
*** Bug 290625 has been marked as a duplicate of this bug. ***
In v1.06 on MacOS X (10.3.9), the preference "Begin finding as you begin typing" controls the *autostart* mechanism of typeaheadfind. However, the checkbox will modify accessibility.typeaheadfind, *NOT* accessibility.typeaheadfind.autostart. In addition, it appears that accessibility.typeaheadfind.autostart is completely ignored (true/false make no difference in behavior), and accessibility.typeaheadfind controls only the autostart mechanism. There appears to be no way to totally disable typeaheadfind because of this.
*** Bug 321418 has been marked as a duplicate of this bug. ***
In v126.96.36.199 for MacOS X, the bug I described in comment #8 is still present... the two typeaheadfind preferences are not behaving properly, as outlined in that comment.
The same problem occurs in Firefox 2.0 beta 1 (20060710) on Windows
Sorry, the problem in the latest Windows beta is that any typing outside a text field will activate type-ahead find, even if accessibility.typeaheadfind.autostart is false. The MozillaZine knowledge base links to this bug for that problem. :-(
*** Bug 348187 has been marked as a duplicate of this bug. ***
2 years ago
Priority: -- → P5
3 months ago
Duplicate of this bug: 1412423
The history of the 'autostart' pref wasn't very clear to me, until I dived a little deeper into CVS and bugzilla history. So this was implemented in bug 176296, which was back when _any_ keystroke would initiate a find-in-page and "'" or "/" were used to switch between text-mode and links-only-mode. Today these keys are used as activators for Quick Find (showing a minimally marked up findbar), and the 'autostart' pref is not used anymore. Additionally, the 'accessibility.typeaheadfind.autostart' and 'accessibility.typeaheadfind.enabletimeout' are not used anymore. Therefore it seems prudent to ensure that 1. 'accessibility.typeaheadfind.autostart = false' disables Quick Find for those who wish it, 2. 'accessibility.typeaheadfind.enabletimeout' is removed from all.js. Upping priority, since this bug is now actionable.
Priority: P5 → P2
You need to log in before you can comment on or make changes to this bug.