Page 1 of 1

[RESOLVED] 2.6.8.40 on fresh install contains nothing

Posted: Wed Sep 10, 2014 5:58 pm
by Just Me
doing fresh install win 7 x64 ultimate SP1 today
> added NoScript 2.6.8.40 from addons.mozilla.org to Firefox 3.6.28 and none of the default options are selected
- I always start with Firefox 3.6.28 because some options are missing from the different dialogs of later versions and are just easier to preset in 3.6.28

eg.
- the white list is empty
- all the default options for the hover menu are unchecked

removed 2.6.8.40
and tried again but no go
also setting the options is not retained
removed 2.6.8.40 again
and installed 2.6.8.36 and all the settings for everything returned to normal

Re: 2.6.8.40 on fresh install contains nothing

Posted: Wed Sep 10, 2014 7:11 pm
by barbaz
Confirmed on Fx 3.6.28/Linux. Options dialog totally broken. Settings don't load, and clicking OK doesn't do anything.

Nothing related in the Error Console.

I'll see if I can find the exact dev build which caused this regression.

Re: 2.6.8.40 on fresh install contains nothing

Posted: Wed Sep 10, 2014 7:18 pm
by barbaz
Seems like this broke with 2.6.8.40rc1... and I was the one who provided that patch :oops:
Sorry about that, I'm not used to developing anything for Gecko < 13.

For now, you'll need to downgrade to NoScript 2.6.8.39rc2

Re: 2.6.8.40 on fresh install contains nothing

Posted: Wed Sep 10, 2014 7:41 pm
by barbaz
Unfortunately I can't find any documentation of browser compatibility of XUL deck, nor am I able to figure out why my patch doesn't work with Fx 3.6.28 :(

ETA Also, in Fx 3.6.28, Cu.reportError and alert run from noscriptOptions.js doesn't generate any messages, making debugging here impossible :?: :?:

Re: 2.6.8.40 on fresh install contains nothing

Posted: Thu Sep 11, 2014 11:23 am
by Giorgio Maone
Please check latest development build 2.6.8.41rc2, thanks.

Re: 2.6.8.40 on fresh install contains nothing

Posted: Thu Sep 11, 2014 5:28 pm
by barbaz
(after looking at the diff for latest dev build: ) Oops :?
Indeed, looks like it broke because I had used a syntax unavailable in Gecko < 13. Nice catch Giorgio.