NoScript doesn't work on 1108 nightly due to Bug 1414096

Bug reports and enhancement requests
Post Reply
koron
Junior Member
Posts: 20
Joined: Wed Jul 18, 2012 1:44 am

NoScript doesn't work on 1108 nightly due to Bug 1414096

Post by koron »

With 1108 nightly, NoScript can't work correctly.
Prefs aren't displayed, some sites returns error.

NoScript uses nsIPrefBranch.setComplexValue which behavior was changed by a patch in Bug 1414096.
So that, NoScript no longer works with 1108 nightly.

ADDITION:
Once, Bug 1414096 is reopened by backout.
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0
Robert84MK
Posts: 5
Joined: Thu Nov 09, 2017 5:41 pm

Re: NoScript doesn't work on 1108 nightly due to Bug 1414096

Post by Robert84MK »

Yes Firefox 58 + No Script 5.1.5 and some site has error (no load) "Connection is not secure" and "Redirect loop"
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0
User avatar
Thrawn
Master Bug Buster
Posts: 3106
Joined: Mon Jan 16, 2012 3:46 am
Location: Australia
Contact:

Re: NoScript doesn't work on 1108 nightly due to Bug 1414096

Post by Thrawn »

NoScript < 10 isn't expected to work with Firefox 57+. Please wait for version 10 (the pure WebExtension version) to post these bugs.
======
Thrawn
------------
Religion is not the opium of the masses. Daily life is the opium of the masses.

True religion, which dares to acknowledge death and challenge the way we live, is an attempt to wake up.
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0
GreenReaper
Posts: 6
Joined: Tue Aug 08, 2017 5:22 pm

Re: NoScript doesn't work on 1108 nightly due to Bug 1414096

Post by GreenReaper »

It is possible to fix it by modifying the files ABE.js, ScriptSurrogate.js, DoNotTrack.js, noscriptOptions.js and Restartless.jsm in the XPI's chrome\content\noscript folder to replace instances of get/setComplexValue to get/setStringPref and dropping the second parameter along the lines demonstrated in the HG Changeset patch. Of course since the signature is no longer valid you then need to load the xpi manually via about:debugging, so a more sensible approach for most people might be to revert to the Beta.
Laurence "GreenReaper" Parry
https://greenreaper.co.uk - https://wikifur.com/ - https://www.flayrah.com/ - https://inkbunny.net/ - https://yerf.metafur.org/
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0
Post Reply