[RESOLVED] Conflict between NoScript & new debugger
Posted: Thu Jun 14, 2012 6:01 am
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!
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!
