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!

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

Stop loading page function doesn't work

  • 2
  • 3
  • 2 views
  • Nzaghachi ikpeazụ nke 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?

Asịsa ahọpụtara

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.

Gụọ azịza a na nghọta 👍 0

All Replies (2)

more options

Asịsa Ahọpụtara

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.