accessibility.typeaheadfind.enabletimeout is ignored

NEW
Unassigned

Status

()

Toolkit
Find Toolbar
P2
normal
13 years ago
5 months ago

People

(Reporter: TGOS, Unassigned)

Tracking

(Depends on: 1 bug, {access})

Trunk
access
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
Find as you type doesn't work on Macs. The new, cute search bar on the bottem
immediately goes away after I typed only one letter and the next letter
immidiately starts a new search, no matter how fast I type.

I set accessibility.typeaheadfind.enabletimeout to false, so it should stay
there forever, but it goes away immediately
(Reporter)

Comment 1

13 years ago
Oh, my current browser version, of course:

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040919
Firefox/0.10

Updated

13 years ago
Component: Search → Find Toolbar / FastFind

Updated

13 years ago
Assignee: p_ch → firefox
QA Contact: firefox.search

Comment 2

13 years ago
Works for me in build 20040920 (branch)

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040920
Firefox/0.10
(Reporter)

Comment 3

13 years ago
Jo, can you do me a favor?
Can you open a new tab and enter "about:config" as address. Then please enter
"typea" into the filter line.

Some lines will be left over. Can you please post all the settings left over
here? I'd like to compare them to my settings. Maybe this explains why it works
for you but not for me. Maybe it's a setting problem.

But then it's still a bug IMHO. No setting should cause such an incorrect behavior.
(Reporter)

Comment 4

13 years ago
Okay, I made some tests myself. The problem is, that 

accessibility.typeaheadfind.enabletimeout

is ignored on the Mac (or it is ignored in general. Have to test it under
Windows this evening).

The setting

accessibility.typeaheadfind.timeout

was set to 0 in my config; this was the way how to disable timout in earlier
versions. But now 0 really means a timeout of 0, so it times out at once.

May I suggest a solution for this problem?

A timeout of 0 should still be treated as "no-timeout", since it makes no sense
to really have a timeout of 0.

And accessibility.typeaheadfind.enabletimeout should be honored when set to
false, regardless of timeout set.
Summary: Find as you type doesn't work any longer on Macintosh → accessibility.typeaheadfind.enabletimeout is ignored
(Reporter)

Comment 5

13 years ago
Confirmed in Windows (XP + SP2)
Assuming it applies to all platforms
OS: MacOS X → All

Comment 6

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

Comment 7

13 years ago
We can close it once the patch has been checked in and I can verify correct
behavior in one of the nightly builds
Depends on: 265915

Comment 8

13 years ago
Confirmed. Running Windows XP Pro SP2, tested with Firefox 1.0.1 and latest
Trunk with clean profiles.

Comment 9

13 years ago
Same thing here (Mozilla/5.0 (Windows; U; Windows NT 5.1; fr-FR; rv:1.7.6)
Gecko/20050223 Firefox/1.0.1)
Find as you type dialog box just appears a microsecond.
accessibility.typeaheadfind.timeout=5000
accessibility.typeaheadfind.enabletimeout=true

Note the Ctrl-F shortcut or menu action just works find : dialog box stay active
indefinitely

Comment 10

12 years ago
This is still broken in Firefox 1.5 RC3. The find bar disappears after 5 seconds even when accessibility.typeaheadfind.enabletimeout is false.

I'm running Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 on Windows XP SP2.

I did a clean install of Firefox 1.5 RC3, not an upgrade, no old preferences or settings.

Extensions I'm using: DOM Inspector, Talkback, Google Toolbar for Firefox

Workaround: Set accessibility.typeaheadfind.timeout to 999999999 and restart Firefox.

Updated

12 years ago
Assignee: firefox → nobody
QA Contact: fast.find
Hardware: Macintosh → All
Version: unspecified → Trunk
(Assignee)

Updated

9 years ago
Product: Firefox → Toolkit

Updated

8 years ago
Keywords: access

Comment 11

3 years ago
20/9/2004: please fix this bug!
Thank you!
Priority: -- → P2
You need to log in before you can comment on or make changes to this bug.