User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9) Gecko/2008061004 Firefox/3.0 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9) Gecko/2008061004 Firefox/3.0 When switching to another application using Cmd-tab, and then using Cmd-tab to switch back into Firefox, keyboard shortcuts (Eg. Cmd-T, Cmd-L, Cmd-K) do not work. The corresponding menu flashes briefly but nothing happens. Keyboard shortcuts are restored to working when the browser window is clicked. Reproducible: Always Steps to Reproduce: 1. Cmd-Tab to another application. 2. Cmd-Tab back into Firefox. 3. Try to open new tab with Cmd-T. Actual Results: The File menu flashes briefly but a new tab is not created. Expected Results: A new tab should be created.
I can't reproduce this (testing on OS X 10.5.3). Please be more precise. For example, tell us what page was displayed in Firefox before you Cmd-Tabbed away from it, and which application you Cmd-Tabbed to (before Cmd-Tabbing back to Firefox). It may also be relevant which other applications were running.
Summary: Keyboard shortcuts not working when apple-tabbing into firefox → Keyboard shortcuts not working after switching to Firefox with Cmd+Tab
I'm having the same problems, although not as reproducible as from the original reporter. This seems to happen quite often, and usually only in one open tab. Switching to another application and back to Fx seems to solve the problem. Also, Ctrl-tab for switching tabs still works, but Cmd-T for a new tab does not. I'm using a MacBook Intel core 2 duo with Leopard 10.5.4. Programs running at the same time: * Finder * Mail * Cog * Transmission * iTunes * Terminal * Activity monitor * QuickSilver
> and usually only in one open tab What does this mean? Does it mean "usually when the browser window has only one tab"?
Steven wrote: > What does this mean? Does it mean "usually when the browser window > has only one tab"? No, it means that it only happens in *one* tab when a few tabs are open. The other tabs do not show this behaviour.
I'm having the same reproducible issues as original post. System Version: Mac OS X 10.5.5 (9F33) Processor 2.2 GHz Intel Core 2 Duo Memory: 4GB 667 MHz DDR2 SDRAM Running Programs: Firefox Mail Skype TextEdit Firefox data: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:18.104.22.168) Gecko/2008102920 Firefox/3.0.4 - Description of "Spaces" functions: switch desktops: i.e. CTRL + (any arrow direction) or select the "Spaces" icon from toolbar and switching desktops that way. Explanation of problem: - restarted computer - only running programs listed above. - switching from Firefox desktop to any other desktop using above "Spaces" methods, then moving back to the desktop containing Firefox causes all shortcuts (CTRL + T, CTRL + W, CTRL + F, etc) to stop working. Results of testing: - On menu bar above, the words "FILE", "EDIT", "VIEW", etc. light up when the shortcut in that menu is selected. For example: pressing CTRL + F highlights the word "EDIT" in the menu bar, but does not bring up the "Find" toolbar at the bottom. Same for all shortcut calls. - To fix, click on the html page that is in current view or Bookmarks Toolbar. Reproducible: - Always
(In reply to comment #5) I can't reproduce this problem, either. Moreover there's no particular reason to think this is the same bug(s) as others have reported here. By default Spaces doesn't allow using key combinations to change desktops. You need to open the Expose & Spaces prefs panel, click the Spaces tab, and choose something for "To switch between spaces". In turn I tried "Command + arrow keys" and "Control + arrow keys" -- with neither one did I see what you report. By the way, you appear to confuse the Command and Control keys. Firefox supports command-t, command-w, and command+f, but not control-t, control-w or control-f. I tested with Firefox 3.0.4 on OS X 10.5.5, with no extensions.
I apologize, I incorrectly stated how to activate the Firefox shortcuts. You are correct, in my explanation of Firefox shortcuts, please replace CTRL + (whatever) with CMD + (whatever). Secondly, I should explain that I am adding on to the original post. You may be correct that it may not be exactly what the original post is stating, therefore, maybe I can spin this off to another post, but at minimum, I am experiencing the same issue. When I tested the CTRL + TAB to another application within the same OS X "space" (sorry, I called them desktops) and back to Firefox, Firefox lost "focus" and you have to click within the current Firefox tab you are looking at in order to use the shortcut commands. If you were typing in a box and followed the steps just stated, when you come back to Firefox, it does not allow you to continue typing within the text field, even when it's highlighted and the cursor is flashing. You must click within the window to gain "focus" again. But with other applications, if you ctrl+tab from firefox to the application, you do not have to click within the application again to continue to type within any fields. I, unfortunately, am experiencing further issues that when I go to another "space" and back, it has the exact same effect. Basically, once I go away from the Firefox application and back, the main window within Firefox looses "focus". I hope this explains the issue further. I understand this is hard to reproduce, I will try to track down what has been installed within the last 3 weeks to see what may have changed. For me I thought it was from the last update from Firefox, but I of course could be wrong. Thank you.
(In reply to comment #7) Try running Firefox in "Safe Mode" (hold down the Option key while you start Firefox), to see if this makes your problem go away. Safe Mode disables all extensions.
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.
Whiteboard: [CLOSEME 2010-11-15]
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.