[RESOLVED] Conflict between NoScript & new debugger

[mauro.sanabria]

Good evening; I use Fx Aurora for normal browsing, as it is stable enough for this purpose. Following this site recommendation I use the latest developer version for NoScript.

Last week Fx Aurora reached the 15.0a2 level and this is the first time I noticed a new tool under the Web Developer menu, namely the Debugger (was it there in 14.0a2?). Unfortunately when I try to activate it via menu it flashes at the window bottom and disappears, leaving only the check mark visible in the menu entry.

After some add-on bisecting it turned out NoScript was the culprit: disabling it allows the Debugger to appear. Moreover, creating a brand new profile and installing only NoScript (this time I tried with the normal release) reproduces the problem, again solved by disabling NoScript. Debugger works alright in this new profile before installing NoScript as well.

The first thing that suggested a conflict was that the new Debugger can be activated by the Ctrl-Shift-S shortcut; however, by default NoScript pops up its menu with this shortcut as well (could be changed via about:config) and the NoScript binding wins over the Debugger one, leaving only the Web Developer menu option to activate the Debugger. Alas, this may not be the cause of the problem described above since yet another add-on (Petr Blahos' Sudoku) uses this shortcut, but this time the Debugger binding wins (when NoScript is disabled or not installed, of course).

Eager to try the new Debugger, for the time being I have disabled NoScript (heresy!); could you please look into this? Thanks for such powerful add-ons (Flashgot user here as well).

BTW, first post. Yay!

[Thrawn]

Hi, Mauro. Thanks for the report; I believe it has already been raised recently. Does that thread help?

[mauro.sanabria]

Hi, Mauro. Thanks for the report; I believe it has already been raised recently. Does that thread help?

Hi Thrawn; my apologies for the late reply, I was totally unable to follow up after my OP. I checked the referred post, but it is not the same issue: this one doesn't have to do with hovering/right-clicking the NoScript icon nor is a crash. After several Aurora updates (and at least one for NoScript) the issue remains. STR:

• Using Aurora 15.0a2, create and use a new profile
• Install NoScript and restart Fx
• Bring up the new debugger with Aurora button -> Web Developer -> Debugger
• Note that the debugger pane flashes for a fraction of a second and disappears, while its menu option remains checked
• Also note that the keyboard shortcut for the debugger (Ctrl+Shift+S) is swallowed by NoScript
• Go to about:addons, disable NoScript and restart Fx
• Now bring up the debugger either with the Aurora button menu or with the keyboard shortcut
• Success!

All of this was tried with Windows 7 32-bit, no other systems currently available. Please tell me whether this is reproducible at your end. Thanks...

[therube]

Working here.

[therube]

Ah.
Working here ... the very first time I attempted.

The second time, a flash , then nothing more:

Code: Select all

Error: [Exception... "Component returned failure code: 0x80470002 (NS_BASE_STREAM_CLOSED) [nsIOutputStream.write]"  nsresult: "0x80470002 (NS_BASE_STREAM_CLOSED)"  location: "JS frame :: chrome://global/content/devtools/dbg-transport.js :: DT_onOutputStreamReady :: line 94"  data: no]
Source File: chrome://global/content/devtools/dbg-transport.js
Line: 94


Code: Select all

    let written = aStream.write(this._outgoing, this._outgoing.length);


So ...

Quit FF
Restart FF
[do NOT hit Ctrl+Shift+S]
Bring up the new debugger with Aurora button -> Web Developer -> Debugger [it should work]
Close Debugger
Bring up the new debugger with Aurora button -> Web Developer -> Debugger == FLASH (& Error Console message).


Restart in Safe Mode, & Debugger works repeatedly, either by menu or shortcut key.


This turned up some very interesting threads (to me) though I don't think pertinent to this issue, https://bugzilla.mozilla.org/buglist.cg ... id=3558223 ?

[mauro.sanabria]

Thrawn, therube, thanks for your replies; the latest NoScript developer version 2.4.8rc3 contains a workaround for this issue as well as changing the old keyboard shortcut which was conflicting with the new debugger. The workaround is for bugzilla bug 771655.

So NoScript works again! Re-enabled; thanks a lot Giorgio!