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!

Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Avatar for Username

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Toś ta nitka jo se archiwěrowała. Pšosym stajśo nowe pšašanje, joli trjebaśo pomoc.

How to make firefox stop loading a site when a new address is entered or a new link/bookmark is clicked?

  • 4 wótegrona
  • 1 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót siggesiege

siggesiege
siggesiege
more options

When you enter an address into the address bar that represents a slow loading site (or even a site that does not exist) and then immediately after hitting enter change the address linking to a site that's loading faster you will get to the latest inputed site. But after a moment firefox will return you to the address you first inputted, either to the site it represents or a page containing a message that the site could not be loaded.

This problem often occurs while typing the incorrect address and quickly after correcting it.

Reproduce the error with the following example: 1: Enter "awaawefawefsdfj.com" (or some other none-existing site) into the address bar and hit enter. 2: Quickly after replace the address with "google.com" (or some other fast loading site) and hit enter.

This will first show the google page, and shortly afterward displaying a page with the error message.

So my question is: Can this annoying issue be fixed with settings?

When you enter an address into the address bar that represents a slow loading site (or even a site that does not exist) and then immediately after hitting enter change the address linking to a site that's loading faster you will get to the latest inputed site. But after a moment firefox will return you to the address you first inputted, either to the site it represents or a page containing a message that the site could not be loaded. This problem often occurs while typing the incorrect address and quickly after correcting it. Reproduce the error with the following example: 1: Enter "awaawefawefsdfj.com" (or some other none-existing site) into the address bar and hit enter. 2: Quickly after replace the address with "google.com" (or some other fast loading site) and hit enter. This will first show the google page, and shortly afterward displaying a page with the error message. So my question is: Can this annoying issue be fixed with settings?

Wubrane rozwězanje

You can provide that feedback to the developers here - https://input.mozilla.org/en-US/feedback

Toś to wótegrono w konteksće cytaś 👍 1

Wšykne wótegrona (4)

the-edmeister
the-edmeister
  • Moderator
more options

Hit the Stop button in the Location Bar before loading the next URL.

siggesiege
siggesiege Pšašaŕ
more options

Yes, and I could also wait until the browser has taken it's time to timeout and then go. However both "solutions" make my life harder and the purpose of a tool is to simplify tasks. Is there even any reason it should redirect you to your first request even after a new request has been made? In my opinion firefox should "hit the stop button" by itself when you submit a new request.

the-edmeister
the-edmeister
  • Moderator
more options

Wubrane rozwězanje

You can provide that feedback to the developers here - https://input.mozilla.org/en-US/feedback

siggesiege
siggesiege Pšašaŕ
more options

Well, I guess I can't have everything instantly. I have posted feedback to the developers through the link you gave. Maybe it will be fixed in the future, although it seems like a low priority issue :)