Avatar for Username

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

Ko téma oñeñongatúma. Ejapo porandu pyahu eikotevẽramo pytyvõ.

Extensions don't work on mozilla.org?

  • 1 Mbohovái
  • 2 oguereko ko apañuãi
  • 4 Hecha
  • Mbohovái ipaháva cor-el

eyeoninf
eyeoninf
more options

None of my Firefox extensions work on mozilla.org. I checked their whitelists and mozilla.org was not in them. There's no message saying that "this extension does not work here". So, for example, if I right click on an element and click uBlock's "Block element", nothing happens whatsoever. Why is this necessary, and is there a setting to change this?

Examples of extensions that don't work on mozilla.org: Greasemonkey, uBlock, Vimium

None of my Firefox extensions work on mozilla.org. I checked their whitelists and mozilla.org was not in them. There's no message saying that "this extension does not work here". So, for example, if I right click on an element and click uBlock's "Block element", nothing happens whatsoever. Why is this necessary, and is there a setting to change this? Examples of extensions that don't work on mozilla.org: Greasemonkey, uBlock, Vimium

Ñemoĩporã poravopyre

Mozilla websites have CSP policy rules that prohibit injecting JavaScript and CSS files in their pages as a security (XSS;cross-site-scripting) measure. This prevents extensions that want to modify the web page from working properly. This is a limitation of WebExtensions in Firefox and most affected extensions state this on their Addons page.

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

Opaite Mbohovái (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Ñemoĩporã poravopyre

Mozilla websites have CSP policy rules that prohibit injecting JavaScript and CSS files in their pages as a security (XSS;cross-site-scripting) measure. This prevents extensions that want to modify the web page from working properly. This is a limitation of WebExtensions in Firefox and most affected extensions state this on their Addons page.