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!

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Firefox prevents a new page from opening? why?

  • 2 Mbohovái
  • 17 oguereko ko apañuãi
  • 2 Hecha
  • Mbohovái ipaháva 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????

Ñemoĩporã poravopyre

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:

Emoñe’ẽ ko mbohavái ejeregua reheve 👍 14

Opaite Mbohovái (2)

more options

Ñemoĩporã poravopyre

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:

Moambuepyre cor-el rupive

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™