InformAction Forums

Thank you for sending your file. It is almost 900KB big and contains more than 30,000 entries (mostly marked as UNTRUSTED). I suspect you've automated some way the population of the UNTRUSTED list, otherwise I would doubt of your sanity :D Please understand NoScript has never been designed (let alon...

Would you mind sending me your NoScript Options>Export file for examination (my email address is listed on the top right of https://maone.net)?
Thanks.

Please check latest development build:
v 11.1.6rc1
============================================================
x Updated TLDs
x [L10n] Updated sv_SE
x Better handling 0 width / 0 height media placeholders

Are you in a private window?
Nevermind, I managed to reproduce on non-private windows as well using https://worldstar.com/video.php?v=wshhPmNY69rqX1BJe3Eo
Looks like some kind of race condition during the placeholder creation. Investigating, thanks.

Could you try about:debugging > "This Firefox", find NoScript among the extensions and press "Inpsect"?
Then select the "Console" tab, clear it, try to reproduce this issue and watch for any error message.

Aak wrote: ↑

Wed Nov 11, 2020 7:20 pm

Maybe to vague indeed. But typing in the duckduckgo url really doesn't do anything. No action at all. The typed in URL even disapears. Disabling Noscript fixes this. I can send you a videocapture if you want.

Could you please try using NoScript Options>Advanced>XSS>Clear XSS Choices?

It cannot, but it usually mitigates many of these attacks which typically: Either insert their scripts dynamically through reflected XSS (which is blocked by NoScript's XSS filter)... ... or, if they manage to statically store malicious scripts in the trusted website, they usually insert minimal boo...

Does this problem happen even if NoScript is the only extension installed?

Does it happen also on a clean profile with just NoScript installed?

Though the url is later updated by Firefox to the correct one, this really seems like a bug. It looks like a Firefox bug, indeed. I cannot reproduce on 83 beta, therefore this has been already (accidentally?) fixed. However I implemented the suggested work-around in latest development build , thank...

Thank you Giorgio, that worked, is there any explanation as to why? Yes. My guess, which you've proved correct, is that you had previously faced a XSS prompt for a request landing on www.googleadservices.com and you selected "Never allow", so my original assumption that something blocked the load b...

Could you try "NoScript Options>Advanced>Clear XSS Choices"?

What most likely happened is that some kind of adblocker, either inside or outside of your browser, prevented the page from even beginning loading, and NoScript's content scripts didn't load either because there was no page to host them. Under these circumstances, NoScript cannot "see" the page (whi...

Do you mean that the random pages you land on are not automatically set to TRUSTED (which is expected, unless you've got the "Temporarily set top-level sites to TRUSTED" option checked, or you've used the "Disable restrictions for this tab" command)? Or that you can't open the links? Are we talking ...

Could you please show me the exact code / page which doesn't work?