Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Firefox prevents a new page from opening? why?

  • 2 antwoorden
  • 17 hebben dit probleem
  • 2 weergaven
  • Laatste antwoord van Lonewolfalpha

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????

Gekozen oplossing

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:

Dit antwoord in context lezen 👍 14

Alle antwoorden (2)

more options

Gekozen oplossing

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:

Bewerkt door cor-el op

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™