NoScript has become somewhat ineffectual

[therube]

NoScript has become somewhat ineffectual.

Strange one here.
The NoScript icon is changing, I can "change" Allow's, but not everything is working as expected.

Perhaps related to opening the same Profile sandboxed (Sandboxie) running an earlier release of SeaMonkey (2.0 vs 2.0.1).

http://www.nonags.com/ will display a message at the top of the page if JavaScript is blocked.
I can toggle JavaScript, but the page does not refresh to reflect the same.

Keyboard shortcut (Ctrl+Sh+\) is not refreshing the page, but when selected from the icon menu, it does.

Similarly http://www.youtube.com/watch?v=nfbOHebi ... rn-2r-4-HM may incorrectly report JavaScript status - until you refresh the page. If the video is playing, Forbidding youtube.com with the shortcut does not stop the video - until you refresh the page. Using the icon menu is working as expected (refreshing the page automatically), thereby allowing or blocking playback.

Code: Select all

Error: Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIPrefService.savePrefFile]
Source file: chrome://noscript/content/Main.js
Line: 1003

Code: Select all

var res = this.prefService.savePrefFile(null);

(Funny that we were just talking about prefs.js.)

Code: Select all

Error: Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsISafeOutputStream.finish]
Source file: file:///C:/TMP/___X_X_X/201b2/X/components/nsSessionStore.js
Line: 2658

Code: Select all

    // write and close stream
    stream.write(convertedData, convertedData.length);
    if (stream instanceof Components.interfaces.nsISafeOutputStream) {
      stream.finish(); <-=== IT IS THIS LINE BEING POINTED TO, 2658
    } else {
      stream.close();

This is likely something of my doing.

[therube]

This is likely something of my doing.

Close down my sandbox, Ctrl+Sh+\ returns back to normal with pages refreshing as expected & the Error Console messages are now gone.

I'll have to think about this :scratcheshead:.

[therube]

Using a different Profile with the sandboxed browser seems to alleviate the problem.

(I would not have normally started a second instance <even sandboxed> using the same Profile, but I was running the .exe directly so had no option to select a Profile on startup.)

There may still be some lingering affects to the current browser session. LIke you may have to kind of "jump start" the Ctrl+Sh+\ shortcut on existing windows to get running.

[Giorgio Maone]

Please check latest development build 1.9.9.24

[therube]

Going through the same steps, I end up with the same results.

Code: Select all

Error: Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIPrefService.savePrefFile]
Source file: chrome://noscript/content/Main.js
Line: 1006

Code: Select all

var res = this.prefService.savePrefFile(null);

Code: Select all

Error: Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsISafeOutputStream.finish]
Source file: file:///C:/TMP/___X_X_X/201b2/X/components/nsSessionStore.js
Line: 2658

Note that in my sandboxed browser, NoScript does continue to work properly.

Should I be expecting different, or is this just something of my doing?
(I know I would expect it not to be an issue, but running sandboxed, you can never know exactly whats going on.)

[Giorgio Maone]

I just wanted to be sure your observations weren't tainted with the other "temporary allow" issue.
That said, the errors you're reporting in this thread are apparently due to a filesystem permission issue (probably caused by your sandbox) which is preventing any preference from being correctly saved. Not NoScript-specific, therefore.