We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

当サイトはユーザー体験を改善するためのメンテナンスを実施中に機能が制限される予定です。記事を読んでもあなたの問題が解決せず質問をしたい場合は、Twitter の @FirefoxSupport、Reddit の /r/firefox で、サポートコミュニティが皆さんを助けようと待機しています。

Mozilla サポートの検索

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.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

When I type an address in the location bar and hit Enter nothing happens. I must click the arrow button at the end of the location bar. How do I fix it so that the Enter key works?

  • 2 件の返信
  • 103 人がこの問題に困っています
  • 1 回表示
  • 最後の返信者: Raudi

more options

When I type a web address in the location bar and hit enter nothing happens. In order to go to the website I've typed in, I must click the arrow button at the end of the location bar. How do I make it so that hitting the enter key takes me to the web page.

This happened

Every time Firefox opened

== Since Firefox 4 Beta installed an update

When I type a web address in the location bar and hit enter nothing happens. In order to go to the website I've typed in, I must click the arrow button at the end of the location bar. How do I make it so that hitting the enter key takes me to the web page. == This happened == Every time Firefox opened == Since Firefox 4 Beta installed an update

すべての返信 (2)

more options

This sort of problem is usually caused by an add-on. Try the options in the troubleshooting extensions and themes article to test if it is an add-on causing the problem - https://support.mozilla.com/en-US/kb/Troubleshooting+extensions+and+themes

One that I have seen causing problems with the location bar in the Firefox 4 beta builds is IE Tab.

この投稿は TonyE により に変更されました

more options

The AVG addon seems to have caused the problem for me. I had it disabled and everything worked. Then I updated to AVG 2011 and the problem occurred. It seems to have reenabled itself after the update. Just disabling it solved the problem.