Jason G Reporter
	Description • 16 years ago

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

This was functioning properly in Firefox 3beta5, but since RC1 and RC2 has not been functioning properly.

Mac / OSX (version 10.5.3 if it matters) allows you to set keyboard shortcuts in the system preferences for application menus.  To launch this control, use the apple menu (operating system level menu) --> System Preferences --> Keyboard & Mouse --> Keyboard Shortcuts.

You can add new entries for a specific application (like Firefox3rc2.app) by clicking on the "+" button, choosing the app from a drop-down list, typing in the exact menu text to trigger ("Home" for my purposes, which is the History Menu --> Home) and then a keystroke (I use command-/).

Launch Firefox3rc2.app, and attempt to use the keyboard shortcut that was set up.  When I try it, I see the menu (History) highlight briefly as it would in other applications as the event was triggered, but no action is actually performed.

I observed that this was working properly in beta5, and have found references to this problem on MacRumors.com's forums, so this is not a problem unique to my computer, as far as I can tell.

Reproducible: Always

Steps to Reproduce:
1. Set keyboard shortcut preference (as described in details)
2. Launch Firefox 3 RC 2
3. Use keyboard shortcut -- action is not performed
Actual Results:  
Menu item is not triggered (e.g., did not load the home page)

Expected Results:  
Menu item should be triggered (e.g., should load home page)

I do have both Firefox 2 and Firefox 3 RC 2 installed in my /Applications directory.  This was the same setup I had with FF3b5 when it was working, so I doubt this is part of the problem, but it is worth mentioning.

	Jason G Reporter
	Comment 1 • 16 years ago

I forgot to mention...  I did try with all add-ins disabled, so this isn't being caused by an add-in.

	Jesse Ruderman
	Comment 2 • 16 years ago

Bug 429824 comment 2 explains why this doesn't work in RC2 despite working in some betas.

	Jason G Reporter
	Comment 3 • 16 years ago

Thanks Jesse, looks like my search for an existing bug was not as accurate as I thought.