Noscript options interface fails after recent update

[Temporary]

I just updated noscript to the latest version (1.9.9.74)
After this update I am unable to use the noscript options dialog. If I change any options the OK failed seems to click but does not save any changes to close the dialog. I am able to navigate to the different tabs but in no case am I able to save my changes. Also the whitelist appears empty when viewed from the options dialog. However if I use the icon in my status bar to manipulate the data it appears to correctly show things that are allowed or untrusted and correctly manipulate them. All embeddings seem to be off - although on the page itself I still see the noscript clickable layer that replaces flash programs, etc.
If you need any more debugging data I am more than happy to provide it.

[Giorgio Maone]

Hmm, are you really posting from the Firefox instance which is failing?
Because the symptoms you're describing are exactly the same of an issue which is specific to Minefield (Firefox trunk), but shouldn't happen on Firefox 3.6.3.
Anyway, please upgrade to latest development build.
If that doesn't help, please turn the javascript.options.showInConsole about:config preference to true and check whether any error message appears in Tools|Error Console when you open the options dialog.

[Temporary]

I'm using 3.6.3 (Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.3) Gecko/20100509 Firefox/3.6.3) and I'm posting from my own computer

Here is the output of my error log showing chrome/JS errors/warnings/messages\

Code: Select all

Warning: reference to undefined property window.gBrowser
Source file: file:///home/XXXXXX/.mozilla/firefox/ojql7ck5.new/extensions/%7B8cca89ed-0225-487a-8d27-f334049f2bf1%7D/resources/8cca89ed-0225-487a-8d27-f334049f2bf1-jetpack-core-lib/securable-module.js -> resource://8cca89ed-0225-487a-8d27-f334049f2bf1-extension-throbber-lib/custom-events.js
Line: 55
 ----------
Warning: reference to undefined property window.gBrowser
Source file: file:///home/XXXXXX/.mozilla/firefox/ojql7ck5.new/extensions/%7B8cca89ed-0225-487a-8d27-f334049f2bf1%7D/resources/8cca89ed-0225-487a-8d27-f334049f2bf1-jetpack-core-lib/securable-module.js -> resource://8cca89ed-0225-487a-8d27-f334049f2bf1-extension-throbber-lib/custom-events.js
Line: 55
 ----------
Error: $$ is not defined
Source file: chrome://noscript/content/iaUI.js
Line: 33
 ----------
Error: $$ is not defined
Source file: chrome://noscript/content/iaUI.js
Line: 33
 ----------
Error: l is null
Source file: chrome://noscript/content/noscriptOptions.js
Line: 557
 ----------
Error: $(c + "Opts") is null
Source file: chrome://noscript/content/noscriptOptions.js
Line: 243
 ----------
Error: $(c + "Opts") is null
Source file: chrome://noscript/content/noscriptOptions.js
Line: 243
 ----------
Error: $(c + "Opts") is null
Source file: chrome://noscript/content/noscriptOptions.js
Line: 243
 ----------
Error: $(c + "Opts") is null
Source file: chrome://noscript/content/noscriptOptions.js
Line: 243
 ----------
Error: Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIWebNavigation.loadURI]
Source file: chrome://global/content/viewSource.js
Line: 221

I attempted to deinstall, remove all about:config options relating to noscript, and reinstall noscript to no avail.
I'll try the development build in a sec and report back here.

[Temporary]

update: development version did not help

[Giorgio Maone]

Those errors are inexplicable (both $ and $$ are defined inside IAUi.js itself).
The only culprit I can think of is an extension conflict. Could you try Standard Diagnostic?

[Temporary]

On a new or different profile (with fewer extensions) no problem.
On my primary profile with all extensions disabled except for noscript - same problem.

[Giorgio Maone]

On my primary profile with all extensions disabled except for noscript - same problem.

All extensions... Jetpacks included?

[Temporary]

I thought jetpacks were now just packaged as XPIs?
Do I need to do something special to disable jetpacks?

[Temporary]

PS - when this is resolved - when noscript auto-updates will it go to the next development version or stable version?

[Giorgio Maone]

PS - when this is resolved - when noscript auto-updates will it go to the next development version or stable version?

It depends. I still can't see where the bug is.
Could you show me a screenshot of your add-ons manager from the profile of yours with all the extensions disabled except NoScript and the options dialog still not working?

[Temporary]

semi-resolved: I reset about:config to the defaults (not just the NS prefs) which fixed the problem. I'm not sure where the conflict is if any. I'll try and keep a log of changed I make and notify you if I find it not working again.
Thanks for the help

[Temporary]

semi-resolved: I reset about:config to the defaults (not just the NS prefs) which fixed the problem. I'm not sure where the conflict is if any. I'll try and keep a log of changed I make and notify you if I find it not working again.
Thanks for the help