409272 - the command+F key stroke fails along with menu button for it as well.

Status: RESOLVED INCOMPLETE

(Firefox :: Keyboard Navigation, defect)

Description

[Jim]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b2) Gecko/2007121014 Firefox/3.0b2
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b2) Gecko/2007121014 Firefox/3.0b2

When using the command+F key stroke nothing happens. The edit menu highlights but nothing else happens. The same goes for when in the edit menu and click on find.

Reproducible: Always

Steps to Reproduce:
1.hit command+F
2. click edit menu tab/button
3. click find
Actual Results:  
When using command+F the edit menu is highlighted but nothing happens.

Expected Results:  
A box search box should have appeared on the bottom of the browser and allowed the search of any text on the page.

Comment 1

[Marcia Knous [:marcia]]

WFM using Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b2) Gecko/2007121014 Firefox/3.0b2.

Please try starting in Safe Mode (http://kb.mozillazine.org/Safe_mode) and see if the problem persists.

Comment 2

[Tyler Downer [He/Him]]

This bug was reported using Firefox 3.0 or older, which is no longer supported. The bug has also not been changed in over 500 days and is still in UNCO.
Reporter, please retest this bug in Firefox 3.6.10 or later using a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles. If you still see this problem, please update the bug. If you no longer see the bug, please set the resolution to RESOLVED, WORKSFORME.

This is a mass search of unconfirmed bugs that have no activity on them, so if you feel a bug was marked in error, just remove the CLOSEME comment in the whiteboard within the next month.

Comment 3

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.