Avatar for Username

تلاش سپورٹ

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

مزید سیکھیں

اس تھریڈ کو آرکائیوکیا گیا تھا۔ اگر آپ کو مدد کی ضرورت ہو تو براہ مہربانی نیا سوال پوچھیں۔

Extensions don't work on mozilla.org?

  • 1 جواب دیں
  • 2 میں یہ مسئلہ ہے
  • 9 دیکھیں
  • آخری جواب بذریعہ 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

منتخب شدہ حل

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.

اس جواب کو سیاق و سباق میں پڑھیں 👍 0

تمام جوابات (1)

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

منتخب شدہ حل

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.