Open Bug 259870 Opened 20 years ago Updated 11 years ago

When focused on a tab, typeahead find doesn't work

Categories

(SeaMonkey :: Find In Page, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

mozilla1.8alpha6

People

(Reporter: csthomas, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: helpwanted)

When I focus on an actual tab, typeahead find / FAYT doesn't work.  May be
related to or a dup of bug 259758, but I don't recall if the focus behavior
changed between 1.7 and trunk (I know we added large focus boxes to indicated a
tab has focus).
Assignee: tabbed-browser → aaronleventhal
Component: Tabbed Browser → Keyboard: Find as you Type
Keywords: helpwanted
You need to look at nsTypeAheadFind::HandleKeyPress and see if you're receiving
key events when the user is focused on a tab. If you are, see how you can
prevent it from exiting early by checking if the focus is within the main
browser tabbar.
Assignee: aaronleventhal → cst
Target Milestone: --- → mozilla1.8alpha6
Assignee: cst → aaronleventhal
Whiteboard: active
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
Status: UNCONFIRMED → NEW
Ever confirmed: true
whether it works depends on sequence of events.

click on tab, type, FAYT works.
ctrl-pgdn to another tab and sometimes it works.
one case where it does not:
1. create and put content in 2 tabs
2. click on tab 1
3. ctrl-pgdn to tab 2
4. attempt FAYT 
5. if it works then repeat steps 2-4

results:
no selection occurs

reproduceable:
always or almost always at step 5, only sometimes on first try (up to step 4)

for these steps, perhaps timing is a factor because I often see the mouse hour glass

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20060531 Minefield/3.0a1

also in SM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060516 SeaMonkey/1.0.2 - though I didn't see the hour glass 
Product: Core → SeaMonkey
Mass un-assigning bugs assigned to Aaron.
Assignee: aaronleventhal → nobody
This may be related to bug 318881
Can't reproduce in SeaMonkey/2.17.1 (X11; Linux x86_64; rv:20.0).
(In reply to chAlx from comment #7)
> Can't reproduce in SeaMonkey/2.17.1 (X11; Linux x86_64; rv:20.0).

(In reply to Michal 'hramrach' Suchanek from comment #6)
> This may be related to bug 318881

Quite possible, but I think that bug got fixed by bug 703522.

Another possibility is that this bug got fixed by bug 345526.
(In reply to comment #8)
> (In reply to Michal 'hramrach' Suchanek from comment #6)
> > This may be related to bug 318881
> 
> Quite possible, but I think that bug got fixed by bug 703522.

Well, the SeaMonkey version of that bug at least.
You need to log in before you can comment on or make changes to this bug.