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 clicking the pencil icon causes the entire page to be reloaded within the editing frame. Clicking any editing/pencil icon on the Tiddlywiki main site with Javascript enabled displays expected behaviour. It only occurs when 11.0.38 and 11.0.39rc6 are running, all prior versions seem to behave normally.
Noscript puts FF in a reload loop
Re: Noscript puts FF in a reload loop
Last edited by barbaz on Thu Aug 20, 2020 3:18 pm, edited 1 time in total.
Reason: fix link
Reason: fix link
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:79.0) Gecko/20100101 Firefox/79.0
-
- Master Bug Buster
- Posts: 244
- Joined: Wed Jan 10, 2018 7:37 am
Re: Noscript puts FF in a reload loop
staticNS.js:104
Is the above actually necessary? The root attributes are already removed in the beginning of this file. Sure, they are put back in the setup(), but they should be subject for the CSP now.
.39rc8 does fix the beforeunload problem, but the problem with alert (blocked DOM) still persists.
Code: Select all
documentCSP.apply(new Set()); // block everything to prevent leaks from page's event handlers
.39rc8 does fix the beforeunload problem, but the problem with alert (blocked DOM) still persists.
Mozilla/5.0 (Windows NT 10.0; rv:78.0) Gecko/20100101 Firefox/78.0
- Giorgio Maone
- Site Admin
- Posts: 9454
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: Noscript puts FF in a reload loop
Please check latest development build:skriptimaahinen wrote: ↑Fri Aug 21, 2020 6:25 am .39rc8 does fix the beforeunload problem, but the problem with alert (blocked DOM) still persists.
v 11.0.40rc1
============================================================
x Handle edge case in file:// pages: policy change and
reload before DOMContentLoaded
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0
- Giorgio Maone
- Site Admin
- Posts: 9454
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: Noscript puts FF in a reload loop
This seems to be fixed to me now (tested on 39rc8 and 40rc1). Please confirm, thanks.TiddlywikiUser wrote: ↑Thu Aug 20, 2020 2:34 pm 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 clicking the pencil icon causes the entire page to be reloaded within the editing frame. Clicking any editing/pencil icon on the Tiddlywiki main site with Javascript enabled displays expected behaviour. It only occurs when 11.0.38 and 11.0.39rc6 are running, all prior versions seem to behave normally.
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0
Re: Noscript puts FF in a reload loop
Is 11.0.39rc6 earlier or later than 11.0.39? I ask, because with NoScript 11.0.39 in Tor Browser 9.5.3 (64-bit) on Windows 10 1909, I see the rapid page re-load issue when opening local TXT and HTML files. It goes away if I disable NoScript.v 11.0.39rc6
============================================================
x Fix reload loops on broken file: HTML documents (thanks
bernie for report)
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:79.0) Gecko/20100101 Firefox/79.0
Re: Noscript puts FF in a reload loop
Issue still persists on both 39rc8 and 40rc1 for me.Giorgio Maone wrote: ↑Fri Aug 21, 2020 7:50 pm This seems to be fixed to me now (tested on 39rc8 and 40rc1). Please confirm, thanks.
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0
Re: Noscript puts FF in a reload loop
Yes indeed. I have the issue as well (Tor Browser: Safer Security Level).
Firefox 79 (fresh profile + NoScript 11.0.39 + everything default): no issue.
Firefox 79 (fresh profile + NoScript 11.0.39 + NoScript configuration like Tor Browser with Safer Security Level): no issue.
I am running Windows 10 2004 and I use the test file with Windows line endings like before.
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:79.0) Gecko/20100101 Firefox/79.0
- Giorgio Maone
- Site Admin
- Posts: 9454
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: Noscript puts FF in a reload loop
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-around, but I hope to have something by Monday.
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-around, but I hope to have something by Monday.
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0