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!

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

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 respostas
  • 103 têm este problema
  • 1 exibição
  • Última resposta de 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

Todas as respostas (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.

Alterado por TonyE em

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.