Este site está com funcionalidades limitadas enquanto realizamos manutenção para melhorar sua experiência de uso. Se nenhum artigo resolver seu problema e você quiser fazer uma pergunta, nossa comunidade de suporte pode te ajudar em @FirefoxSupport no Twitter e /r/firefox no Reddit.

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.

Stop loading page function doesn't work

  • 2 respostas
  • 3 têm este problema
  • 12 visualizações
  • Última resposta de galeas

more options

When trying to stop loading a faulty or incomplete url the browser still either loads some page or loads a search engine. Only way I found to circumvent this unwelcome feature is to press the stop loading page shortcut several times.

The problem probably lies in the browser doing the loading request TWICE (or more) instead of once. Meaning that just hitting that stop button once will have no effect, because you only stopped one request, leaving the other one still active...

So my question is: How do I stop this unwelcome behavior?

When trying to stop loading a faulty or incomplete url the browser still either loads some page or loads a search engine. Only way I found to circumvent this unwelcome feature is to press the stop loading page shortcut several times. The problem probably lies in the browser doing the loading request TWICE (or more) instead of once. Meaning that just hitting that stop button once will have no effect, because you only stopped one request, leaving the other one still active... So my question is: How do I stop this unwelcome behavior?

Solução escolhida

Hello,

Try Firefox Safe Mode to see if the problem goes away. Safe Mode is a troubleshooting mode, which disables most add-ons.

(If you're not using it, switch to the Default theme.)

  • You can open Firefox 4.0+ in Safe Mode by holding the Shift key when you open the Firefox desktop or Start menu shortcut.
  • Or open the Help menu and click on the Restart with Add-ons Disabled... menu item while Firefox is running.

Once you get the pop-up, just select "'Start in Safe Mode"

If the issue is not present in Firefox Safe Mode, your problem is probably caused by an extension, and you need to figure out which one. Please follow the Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems article for that.

To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.

When you figure out what's causing your issues, please let us know. It might help other users who have the same problem.

Thank you.

Ler esta resposta 👍 0

Todas as respostas (2)

more options

Solução escolhida

Hello,

Try Firefox Safe Mode to see if the problem goes away. Safe Mode is a troubleshooting mode, which disables most add-ons.

(If you're not using it, switch to the Default theme.)

  • You can open Firefox 4.0+ in Safe Mode by holding the Shift key when you open the Firefox desktop or Start menu shortcut.
  • Or open the Help menu and click on the Restart with Add-ons Disabled... menu item while Firefox is running.

Once you get the pop-up, just select "'Start in Safe Mode"

If the issue is not present in Firefox Safe Mode, your problem is probably caused by an extension, and you need to figure out which one. Please follow the Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems article for that.

To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.

When you figure out what's causing your issues, please let us know. It might help other users who have the same problem.

Thank you.

more options

Hi,

so I tried to run Firefox in safe mode and the problem didn't happen. After some experiments with add-ons I can safely say, that the problem is caused by the "NoScript" add-on. Other add-ons I have installed doesn't seem to affect this in any way.

Thank you for your help.