Thanks - for answers & the code.
I assume because I first blocked scripts globally (as a test) & it didn't prevent the new "ad" window, that a script wasn't causing it.
Right or wrong, that's what happened. In fact, it went on after I changed to block scripts globally, after closing & reopening the main site, etc.
Until ??? I clicked ON the pop up window & marked the URL (listed in the window address bar) as untrusted. That's what I'm saying, it seemed that "blocking all scripts on all sites" didn't solve it. But marking the pop up URL as untrusted... did solve it? Shouldn't those 2 actions have done the same thing?
In this case, it was trickier to see how to block the window (not being an expert). On a (full) browser window pop up ... NoScript won't show the URL of that window - to mark untrusted, unless you click ON the window - AFAIK. Normally, you don't "click on crap" that pops up, because of risks - yes? Not knowing what's really there.
Seems like some risk, having to do that (for this case) before NoScript can / will show the domain to allow marking untrusted?
Don't know if there'd be a way to change NoScript behavior so you wouldn't have to click the new window, to be shown a domain? I'm sure that's part of why they made a separate pop up window - to make harder to avoid.
But here, (seems) even if I'd wanted to leave scripts blocked globally, it didn't seem to affect this one. Unless there was a "glitch" in NoScript recognizing the setting.
I'm positive I first blocked scripts globally & it didn't stop the pop up. After the global blocking, a couple other "good" sites complained about javascript being off, so apparently it was.
I'm just guessing as to why blocking scripts globally didn't stop the problem. I've made lots of setting changes in Fx, other apps - where it was "set to do xyz," but didn't. At times, toggling a setting AGAIN will make it start working. I must be missing something.
I understand the code you wrote (mostly). What is it actually telling NoScript to / not to do (the 1st entry)?
Does inserting those 2 entries add * new * function to NoScript, or modify existing ones?
I assume because I first blocked scripts globally (as a test) & it didn't prevent the new "ad" window, that a script wasn't causing it.
Right or wrong, that's what happened. In fact, it went on after I changed to block scripts globally, after closing & reopening the main site, etc.
Until ??? I clicked ON the pop up window & marked the URL (listed in the window address bar) as untrusted. That's what I'm saying, it seemed that "blocking all scripts on all sites" didn't solve it. But marking the pop up URL as untrusted... did solve it? Shouldn't those 2 actions have done the same thing?
In this case, it was trickier to see how to block the window (not being an expert). On a (full) browser window pop up ... NoScript won't show the URL of that window - to mark untrusted, unless you click ON the window - AFAIK. Normally, you don't "click on crap" that pops up, because of risks - yes? Not knowing what's really there.
Seems like some risk, having to do that (for this case) before NoScript can / will show the domain to allow marking untrusted?
Don't know if there'd be a way to change NoScript behavior so you wouldn't have to click the new window, to be shown a domain? I'm sure that's part of why they made a separate pop up window - to make harder to avoid.
But here, (seems) even if I'd wanted to leave scripts blocked globally, it didn't seem to affect this one. Unless there was a "glitch" in NoScript recognizing the setting.
I'm positive I first blocked scripts globally & it didn't stop the pop up. After the global blocking, a couple other "good" sites complained about javascript being off, so apparently it was.
I'm just guessing as to why blocking scripts globally didn't stop the problem. I've made lots of setting changes in Fx, other apps - where it was "set to do xyz," but didn't. At times, toggling a setting AGAIN will make it start working. I must be missing something.
I understand the code you wrote (mostly). What is it actually telling NoScript to / not to do (the 1st entry)?
Does inserting those 2 entries add * new * function to NoScript, or modify existing ones?