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!

Ko tenda hembiapoite sa’ivéta oñemba’apokuévo hese hembiapo porãve hag̃ua. Peteĩ jehaipyre nomoĩporãiramo ne apañuái ha eporanduséramo, roguerekohína ore nepytyvõ rekoha ikatútava ndeykeko @FirefoxSupport Twitter-pe ha avei /r/firefox Reddit-pe.

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

NoScript Incompatible with Firefox Forum?

more options

When I go to the Firefox forum (e.g., this page), NoScript gives a ? and reports, "In order to operate on this tab, NoScript needs to reload it. Proceed?" Clicking OK just leads back to the same condition. Is this a problem with NoScript or with the Firefox Forum Website? I'm using Firefox 60.0.2 64-bit on a Windows 7 computer. -- jclarkw

When I go to the Firefox forum (e.g., this page), NoScript gives a ? and reports, "In order to operate on this tab, NoScript needs to reload it. Proceed?" Clicking OK just leads back to the same condition. Is this a problem with NoScript or with the Firefox Forum Website? I'm using Firefox 60.0.2 64-bit on a Windows 7 computer. -- jclarkw

Opaite Mbohovái (7)

more options

Hi, no it means you need to turn off NoScript to view the page or leave it on to not view the page. It is working properly. NoScript is a security measure and will always have to decide if to turn it on or off and is it worth turning it on or off.

If you have questions about NoScript please see the Developers URL https://addons.mozilla.org/en-GB/firefox/addon/noscript/ which shows the Developers Homepage, Support Site and Support Email.

Please let us know if this solved your issue or if need further assistance.

more options

I got this helpful response from https://forums.informaction.com/viewtopic.php?f=8&t=24974&p=97533#p97533:

"support.mozilla.com is one of the restricted (extensions.webextensions.restrictedDomains) domains where NoScript cannot function [meaning that it cannot block scripts there, so the scripts are running fine already] due to design decision by Mozilla. Unfortunately the message in the popup that should explain this is wrong. It is a known NoScript bug and hopefully will be fixed soon."

Unfortunately this raises another question: In Firefox 60.0.2 why is it that this forum (e.g., this page) doesn't function correctly? I have to go into (cringe!) Internet Explorer to start a new thread, give feedback, or post replies, which seems absurd for Mozilla's own website!

Since it apparently isn't NoScript that's interfering with this site, it must be something else. Any suggestions? Or maybe I have to start a new thread for this? -- jclarkw

Moambuepyre jclarkw rupive

more options

OPS! -- Looks like Sandboxie (in which I'm running Firefox) is the culprit: I just tried to post this reply from an non-sandboxed instance of Firefox, and it worked fine (although IE doesn't suffer from this problem)! Now I have to track down the issue with Sandboxie -- not your problem... -- jclarkw

Moambuepyre jclarkw rupive

more options

Could be the permissions issue discussed here:

more options

jclarkw said

Now I have to track down the issue with Sandboxie -- not your problem...

Please do report back on it, in case other users are encountering a new issue due to Sandboxie.

more options

cor-el said

Could be the permissions issue discussed here...

I see that "support.mozilla.org" is indeed listed in the comma-separated string for the "extensions.webextensions.restrictedDomains" preference. Before I start deleting things, however, I need to understand better what you are suggesting. Could this explain why the site works properly when Firefox runs outside a sandbox but not when inside? -- jclarkw

more options

I don't think the list of sites where extensions are restricted has anything to do with how the site works, only with whether extensions can touch pages on the site.