InformAction Forums

Please check latest development build:
v 11.0.41rc1
============================================================
x Fixed regression: events suppressed on file:// pages
unless scripts are allowed
x Updated TLDs

Unfortunately, I'm having a new issue with the combination of NoScript 11.0.40 and the Tor browser. Most mouse operations (right-click menu, wheel scroll, etc.) other than link clicking and scroll bar operations are no longer working for local files (file:///). Yes, i can see the regression: unless...

Have you got an idea of the discarded/live ratio of those tabs? Does the problem happen right away after session restore (when most tabs should be discarded), or there's a minimum of live tabs to trigger it? Asking because I wrote a script opening 1600 tabs over 2 windows rotating across 4 urls, but...

No, it's a bug due to a Tor Browser specific behavior (wiping out window.name on every document load).
It's fixed in latest development build.
v 11.0.40rc2
============================================================
x Avoid synchronous policy fetching whenever possible

If this problem surfaced "in the past couple weeks", there are good chances latest development build can fix it. Please check it, thank you:

v 11.0.40rc2
============================================================
x Avoid synchronous policy fetching whenever possible

It's a very different issue in Tor Browser, unfortunately, even though the effect is the same. The Tor Browser erases window.name on each load, therefore completely screwing up current persistence hack. It got very complicated at this point and I've been working for several hours on a further work-a...

This issue seems related to one I've been having with local files. Downloading an empty copy of Tiddlywiki (blue "Download Empty" button at https://tiddlywiki.com/static/GettingStarted.html ) and running it locally (with javascript enabled) in Firefox 79, then editing the GettingStarted entry by cl...

.39rc8 does fix the beforeunload problem, but the problem with alert (blocked DOM) still persists. Please check latest development build : v 11.0.40rc1 ============================================================ x Handle edge case in file:// pages: policy change and reload before DOMContentLoaded

Please check latest development build : v 11.0.39rc6 ============================================================ x Fix reload loops on broken file: HTML documents (thanks bernie for report) x [XSS] Updated HTML event attributes (These changes and the 11.0.39rc6 tag are missing from Github, and the...

Please check latest development build:

v 11.0.39rc6
============================================================
x Fix reload loops on broken file: HTML documents (thanks
bernie for report)
x [XSS] Updated HTML event attributes

It actually looks to be the break in this line that is doing it (not necessarily 1024 spaces): Yes indeed. I do not get the reload loop without the break either. Yes! Interestingly enough, it must be a CRLF: I did not get the loop until I added the 1024 bytes (not necessarily spaces) as suggested b...

I've finally managed to reproduce it, only by adding about a thousand whitespaces before the <meta http-equiv="content-type" content= "text/html; charset=us-ascii"> element. Did you omit the whitespace when pasting or it is actually not there in your samples? Or maybe there's something in your confi...

OK, thanks for the sample. Please understand I keep asking for information because I can't reproduce on my side with several local HTML files, which may differ from yours in some significant way, though. Also, did you try on a clean profile? Thank you. [EDIT] I've tried your sample, and it doesn't l...

Sorry , I thought I had mentioned: I *DID* try the 39rc5 version and the problem still happened. I've now reverted to .97 and turned off auto-updating and it is fine. Sorry if I insist: are you double sure that you've tried rc5 (and not just rc4 as you previously mentioned)? Because otherwise it's ...

"removed" .38 and installed .37 and the problem is gone. YAY Glad to hear it worked for you. But not to incur in the same problem again when you're updated to .39 stable, please check whether latest development build fixes this issue for you: v 11.0.39rc5 ===========================================...