Well, unfortunately there is nothing to be seen at this point.
I used the expected FF (MS) fix.
Start all over again.
So I wiped out my Profile, reinstalled the older 69 build that I had downloaded the other day, then reinstalled NoScript.
And that worked.
Just now updated to 20190603160429, & NoScript continues to work - as one would expect.
But that was not the case yesterday.
I'd not done anything odd, different, that comes to mind.
I had a working system.
FF was bugging me to update.
So I put in an update.
And I then had a broken system.
FF again bugged me to update.
Put that one in, also.
Put back in the older FF that I had download.
Deleted compatibility.ini (to bypass the "oh, you've launched an older version" kind of crap).
Still NoScript failed.
Then I took the expected FF (MS) route & simply wiped everything out.
(Much like how FF 67 RELEASE users are finding they're now having troubles with new or unwanted Profiles opening - but that is not a bug, that is their
Anyhow, an old FF, & current NoScript - everything afresh, worked.
And now, with you not seeing any issue, I (again) updated FF (to today's build, full .mar, as it was) & things continue to work.
So you tell me?
Seems I had an unsent crash, https://crash-stats.mozilla.org/report/ ... af50190604
I wasn't aware that I had
crashed (from a couple days back)?
But as it seems to be a "shutdown" (ShutDownKill) crash & seems as though there are rather, a few ... oh, you know why I didn't know there was a crash - well maybe, or no, I still should have known no?
Anyhow, that little 'ol thing, named "trust", as the trust factor with Mozilla is gone, so I try to "save" myself as much as possible from them, so in Options, I disable "telemetry" crap, & in that case, I also disabled Error Reporting, so that is why the report was not sent. (Thought I did get, just now, a "message" stating that I had an unset crash report.)
I did not know that I had a crash.
Maybe a shutdown crash is expected not to make itself "known" (generally), instead expected to fail, silently, likewise the report expected to be sent, by default, so also silently? (And in that way, a user isn't particularly aware of all the issue that may exists, as they're simply being silently reported. So if they don't actually go out & look... ?)
Maybe this (unknown) "crash" buggered things up & caused this whole situation?
So... is that the deal, that Quantum is so unstable - at any point in time, has so much crap being torn out of it - in an ongoing basis, new "features" being added into it - in an ongoing basis, being such a morass, that it is now in a perpetual state of chaos, that the only feasible "solution" to a problem is to "start over". So that's why they're continually forcing new Profiles on you, why there so adamant about not "going back" (using "today's" Profile with "yesterday's" build). They cannot even trust themselves. That's bad.
Isn't this so Microsoft. Sad.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus