InformAction Forums

NoScript Not Working 69 Nightly ?
Perhaps broken with today's Nightly?
(Hmm. About tells me to update - which just did.)


69.0a1
20190603101337
https://hg.mozilla.org/mozilla-central/ ... 4d50152bb5
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0

NoScript 10.6.2 (I'll update, in a bit)

Allow Globally

URL: https://www.yahoo.com/ ("truncated" display, as in only 1 "page" displays [rather then a "continuous, never ending" page])
URL: https://www.msn.com/ (page is "all there", except on graphics at the very top, all other "pictures" are "blank")
URL: https://www.youtube.com/ ("truncated" display & no graphics)

Anyone confirm?

Man, there are so many 9:13's, I don't know which to note; John, Matthew, Daniel, Numbers, 2 Corinthians, & on & on.


Updated: FF, 20190603160429, no change
NoScript: 10.6.3rc7, no change


Assuming update history is accurate (?) [freakin' can't copy from the dialog - morons]:
20160602094449 I believe worked, must have.

Reverting to 20190531214840, & ignoring FF's "I've launched an older version of FF" warning & still things are not working?

So, throw the Profile away & try again.

Working (with 20190531214840, that is).

therube wrote: ↑Mon Jun 03, 2019 11:19 pm Man, there are so many 9:13's,

log.js 9:13 is inside a generic console logging function - https://github.com/hackademix/noscript/ ... /log.js#L9

therube wrote: ↑Mon Jun 03, 2019 11:19 pm Updated: FF, 20190603160429, no change
NoScript: 10.6.3rc7, no change

Just tried 20190603160429, both with 10.6.2 and 10.6.3rc7 work for me: the three sites you've mentioned (msn, yahoo and youtube) are displayed correctly, no matter whether the domains are individually TRUSTED, or the restrictions are disabled globally or by tab.

Did you try on a clean profile and a fresh NoScript?
If not, can I see your NoScript Options>Export file?

Thanks!

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.
Still broken.

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 doing .)

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.

(Bump, in case you're reading, as I've update the above, any number of times now.)