This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Command+Return and Shift+Return keyboard shortcuts stopped working

  • 1 پاسخ
  • 1 has this problem
  • 2 views
  • آخرین پاسخ توسّط socalbarrister

more options

I'm using Firefox 4.0 on a 21.5" iMac running Mac OS X version 10.6.7. Just this morning, the command+return and shift+return keyboard shortcuts to auto-complete the .com and .net addresses of websites stopped working. Command+w still closes a tab, and command+left click still opens a tab in a new window. However, when I type anything in the address bar ("mac" for example) and then hit command+enter, Firefox opens up a new tab with a Google search for the word I typed. The address for this new tab is as follows:

http://www.google.com/search?q=mac&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a

Any idea what gives? I'm rather perplexed and frustrated.

I'm using Firefox 4.0 on a 21.5" iMac running Mac OS X version 10.6.7. Just this morning, the command+return and shift+return keyboard shortcuts to auto-complete the .com and .net addresses of websites stopped working. Command+w still closes a tab, and command+left click still opens a tab in a new window. However, when I type anything in the address bar ("mac" for example) and then hit command+enter, Firefox opens up a new tab with a Google search for the word I typed. The address for this new tab is as follows: http://www.google.com/search?q=mac&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a Any idea what gives? I'm rather perplexed and frustrated.

All Replies (1)

more options

Just removed OmniBar and the problem went away.