NoScript 2.6.3 suddenly blocks Firefox plugin check page

[scripteze]

Never seen this before updated to Fx 17 & NS 2.6.3.
It appeared that fonts were being blocked. Though I'm a very technical person, I'm not a coder nor a dedicated student of NS (a "NoScript-ie").

Noticed white list contained "mozilla.net," but not mozilla.org. If you enter address, mozilla.net, it redirects to mozilla.org. So, (after much pondering why the plugin check site suddenly didn't work), added mozilla.org to white list. That made check site work, but doesn't answer any questions.

[therube]

Thinking that mozilla.net is there only because extensions are served from there.

[scripteze]

Thanks, but that answer isn't remotely connected to my question. I didn't ask why mozilla.net was there, or why any other domain was / wasn't white listed.

If NS blocks the MOZILLA plugin check site, then I'm guessing it'd block pretty much any site, that isn't either white listed or allowed - partially, temporarily.

[therube]

> it'd block pretty much any site, that isn't either white listed or allowed

Basically yes.
It would block JavaScript on any site, that isn't either white listed or allowed.

[DJ-Leith]

> it'd block pretty much any site, that isn't either white listed or allowed

Basically yes.
It would block JavaScript on any site, that isn't either white listed or allowed.

Hi scripteze, therube is quite correct.

Just to add more detail.

My Whitelist has "addons.mozilla.org"
BUT no other 'mozilla' domains (NO mozilla.com, mozilla.org, mozilla.net etc).
So when I use the plugin check, which I do frequently - is is very useful - I just TA (Temporarily Allow) "mozilla.org"
and then the JavaScript will run and check my Plugins.

DJ-Leith

[Thrawn]

Thanks, but that answer isn't remotely connected to my question. I didn't ask why mozilla.net was there, or why any other domain was / wasn't white listed.

If NS blocks the MOZILLA plugin check site, then I'm guessing it'd block pretty much any site, that isn't either white listed or allowed - partially, temporarily.

I didn't actually see a question in your original post, but if you were asking why mozilla.org isn't whitelisted by default, it's because they didn't need to be for NoScript to work. The default whitelist is very short; other decisions are up to you.