Find as you type = off pref, should respect typeaheadfind and not allow autostart

NEW
Unassigned

Status

()

Toolkit
Find Toolbar
P2
normal
14 years ago
3 months ago

People

(Reporter: Peter6, Unassigned, Mentored)

Tracking

(Depends on: 1 bug)

1.8 Branch
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [good-next-bug])

(Reporter)

Description

14 years ago
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).

Comment 1

14 years ago
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
(Reporter)

Comment 2

13 years ago
*** Bug 264814 has been marked as a duplicate of this bug. ***
No longer depends on: 251073
(Reporter)

Comment 3

13 years ago
(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 ?

Comment 4

13 years ago
(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.

Comment 5

13 years ago
this bug is fixed with the patch in bug 265915
Depends on: 265915
(Reporter)

Comment 6

13 years ago
*** Bug 290625 has been marked as a duplicate of this bug. ***

Comment 7

13 years ago
Possibly related to bug 220900?
Depends on: 220900

Comment 8

13 years ago
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.

Comment 9

12 years ago
*** Bug 321418 has been marked as a duplicate of this bug. ***

Comment 10

12 years ago
In v1.5.0.1 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. 

Updated

12 years ago
Assignee: firefox → nobody
QA Contact: fast.find

Comment 11

12 years ago
The same problem occurs in Firefox 2.0 beta 1 (20060710) on Windows

Comment 12

12 years ago
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. :-(

Comment 13

12 years ago
*** Bug 348187 has been marked as a duplicate of this bug. ***

Updated

11 years ago
Blocks: 363083

Updated

10 years ago
Version: 1.0 Branch → 2.0 Branch
(Assignee)

Updated

10 years ago
Product: Firefox → Toolkit

Updated

8 years ago
Duplicate of this bug: 532642

Updated

2 years ago
See Also: → bug 1210212
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.
Mentor: mdeboer@mozilla.com
Priority: P5 → P2
Whiteboard: [good-next-bug]
You need to log in before you can comment on or make changes to this bug.