Hi, I would not know what has changed on the page. We do not have a before and after look at the code on the unnamed URL. Please see the Developers FAQ page and the Support page : https://addons.mozilla.org/en-US/firefox/addon/noscript/

Mozilla only ok's Extensions submitted by Developers to be used with Firefox. They ok them only and give the Developer a web page to distribute their Extension from. this Extension has a Support link and a Forum Link please check there.

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

NoScript FAQ's are here: https://noscript.net/faq

And the NoScript Support forum is here: https://forums.informaction.com/viewforum.php?f=3

Thank you.

I would not have asked my questions here before checking at each of the links suggested, and after repeated more general searches for information.

I would still like to know what a "privileged page" is.

Knowing that, perhaps I'd have more insight into how the particular page in question might have been changed.

"Privileged page" has to do with your marking a URL as "Trusted" in NoScript.

As far as a particular page not being completely "trusted" when it has been in the past, perhaps that page has changed a bit like with a change in what scripts on that page have been changed or added which could make a part of that page not trusted all of a sudden.

That's the best I can explain the situation. I use NoScript as I have for years, but I am now very liberal as to what I allow to pass thru NoScript due to it being a "pain" to use. NoScript value to me is more with XSS than with blocking a lot. Best to post in the NoScript forum to get an answer from users who are very into using NoScript and all its features.

I get that message on pages where no WebExtensions are allowed to operate, for example:

• internal pages like about:addons
• https://addons.mozilla.org/en-US/firefox/ (screenshot attached)

In my opinion, you shouldn't see it on regular websites.

Firefox 60 will have a preference where you can manually remove individual Mozilla sites from the protected list. (Whether that is a good idea is another question...)

Thank you.

The site in question is one I wouldn't feel a need to restrict via NoScript. So its sudden change was a surprise. Your answers suggest to me that the "change" was to some aspect of the site itself.

I will contact the site owner to let them know of my experience, and to see if I can restore access.

Thanks again.

It occurred to me after posting my reply that if the page you are trying to get to wasn't loading, Firefox may have been displaying an error page. The message may have been related to the error page instead of the site itself. Or in other words, your connection problem may be totally unrelated to NoScript. It's easy enough to temporarily turn off NoScript completely on the Add-ons page to test.

Thank you, jscher2000.

A test that I wish had occurred to me! Sometimes it really does take a different perspective...

I did turn off NoScript, as you suggested, and the page loaded.

Thanks again, to you and the-edmeister and Pkshadow for helping.