Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

Firefox prevents a new page from opening? why?

more options

Each time I click on a link in my email, I get an error msg after a new tab is opened:

"Firefox prevented this page from automatically redirecting to another page"

And I have to always click the tab that says "ALLOW" Why????

Each time I click on a link in my email, I get an error msg after a new tab is opened: "Firefox prevented this page from automatically redirecting to another page" And I have to always click the tab that says "ALLOW" Why????

Vald lösning

See:

  • Firefox > Preferences/Preferences > Advanced > General : Accessibility : [ ] "Warn me when web sites try to redirect or reload the page"

The setting in "Options/Preferences > Advanced > General" is meant as an accessibility feature, as you can see by the label of that section, so that people with disabilities or people who use screen readers do not get confused and is not meant as a safety protection to stop redirecting.

See also:

Läs svaret i sitt sammanhang 👍 14

Alla svar (2)

more options

Vald lösning

See:

  • Firefox > Preferences/Preferences > Advanced > General : Accessibility : [ ] "Warn me when web sites try to redirect or reload the page"

The setting in "Options/Preferences > Advanced > General" is meant as an accessibility feature, as you can see by the label of that section, so that people with disabilities or people who use screen readers do not get confused and is not meant as a safety protection to stop redirecting.

See also:

Ändrad av cor-el

more options

Thank you! . . . I thought I had clicked and unclicked everything that was relevant to this thorny problem, but apparently not.

I never had this Firefox problem before, when I used previous versions over the years (I guess Firefox default checked-it in a new version).

Cor-el, may you always catch your prey. /Lonewolf™