Nasty Firebug's console.log() issue with NoScript 2.1.0.1
-
- Posts: 6
- Joined: Fri May 27, 2011 10:56 am
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
At the risk of talking to myself, its still an issue in 2.1.1
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
I am finding this problem too - in fact, not just console.log, but nothing typed into the Firebug command line will output - even if you type in "window" for example, instead of getting a clickable window DOM object, you just get the window string output.
This happens with Firebug 1.7.3 or Firebug 1.8 betas (any)
The only things I've noticed that have major changes is
1) Firefox 5 upgrade
2) New ver of NoScript (2.1.1.1)
The other odd thing: yesterday I had no issues using Firebug 1.8 beta 4 with NoScript on FFx. Having tried an older beta (for another issue) and then put back Firebug 1.8 beta 4, now that also doesn't work with NoScript enabled. I have to disable NoScript now to get the Firebug console to output anything from the command line or when inserting console.log etc in JS code.
I don't really want to start a new profile as the one I am using has a lot of valuable things in it. Is there a proper way to fully uninstall NoScript because uninstalling it and reinstalling it still seems to cause problems (I can no longer get Firebug 1.8 beta 4 to work like it was working yesterday). Maybe there are additional files to clean up after uninstalling it?
This happens with Firebug 1.7.3 or Firebug 1.8 betas (any)
The only things I've noticed that have major changes is
1) Firefox 5 upgrade
2) New ver of NoScript (2.1.1.1)
The other odd thing: yesterday I had no issues using Firebug 1.8 beta 4 with NoScript on FFx. Having tried an older beta (for another issue) and then put back Firebug 1.8 beta 4, now that also doesn't work with NoScript enabled. I have to disable NoScript now to get the Firebug console to output anything from the command line or when inserting console.log etc in JS code.
I don't really want to start a new profile as the one I am using has a lot of valuable things in it. Is there a proper way to fully uninstall NoScript because uninstalling it and reinstalling it still seems to cause problems (I can no longer get Firebug 1.8 beta 4 to work like it was working yesterday). Maybe there are additional files to clean up after uninstalling it?
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Got a bit more info if it helps:
In the Firefox 5 Web Console (Ctrl-shift K) I see the following message:
[12:07:10.265] The Web Console logging API (console.log, console.info, console.warn, console.error) has been disabled by a script on this page.
This happens with NoScript enabled (even when Allow Global Scripts is set to true)
In about:config, I set noscript.consoleLog and consoleDump to true and 1 respectively and restart Firefox and still no luck... [update 1: realized consoleLog/DUmp are to log/dump NoScript output - though I don't even see those]
[update 2: created brand new FFx 5 profile. Installed firebug 1.7.3 then NoScript. Still cannot write anything from command line (e.g. window) to the console). Then installed latest Firebug 1.8 beta 4 and same problem. Disabled NoScript and it worked.]
In the Firefox 5 Web Console (Ctrl-shift K) I see the following message:
[12:07:10.265] The Web Console logging API (console.log, console.info, console.warn, console.error) has been disabled by a script on this page.
This happens with NoScript enabled (even when Allow Global Scripts is set to true)
In about:config, I set noscript.consoleLog and consoleDump to true and 1 respectively and restart Firefox and still no luck... [update 1: realized consoleLog/DUmp are to log/dump NoScript output - though I don't even see those]
[update 2: created brand new FFx 5 profile. Installed firebug 1.7.3 then NoScript. Still cannot write anything from command line (e.g. window) to the console). Then installed latest Firebug 1.8 beta 4 and same problem. Disabled NoScript and it worked.]
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
- Giorgio Maone
- Site Admin
- Posts: 9524
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Could you check latest development build 2.1.1.2rc9?
Mozilla/5.0 (Windows NT 5.2; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Many thanks for the reply. I didn't see rc9 but saw 2.1.2rc1 and that seemed to have worked from my initial testing so far. Many thanks for that.Giorgio Maone wrote:Could you check latest development build 2.1.1.2rc9?
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
I can still reproduce the old problem, the error console output i see this in the error console when running a command that fails:Giorgio Maone wrote:Could you check latest development build 2.1.1.2rc9?
Code: Select all
Error: Firefox is not defined
Source File: resource://firebug_rjs/commandLine.js
Line: 426
Edit: Using:
Mozilla/5.0 (X11; Linux x86_64; rv:7.0a1) Gecko/20110627 Firefox/7.0a1
and NoScript 2.1.2rc1
Mozilla/5.0 (X11; Linux x86_64; rv:7.0a1) Gecko/20110627 Firefox/7.0a1
- Giorgio Maone
- Site Admin
- Posts: 9524
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Which Firebug version is compatible with Firefox Nightly, exactly?Cork wrote:Giorgio Maone wrote: Edit: Using:
Mozilla/5.0 (X11; Linux x86_64; rv:7.0a1) Gecko/20110627 Firefox/7.0a1
and NoScript 2.1.2rc1
Mozilla/5.0 (Windows NT 5.2; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Firebug 1.8b => http://getfirebug.com/releases/firebug/1.8/Giorgio Maone wrote:Which Firebug version is compatible with Firefox Nightly, exactly?Cork wrote:Giorgio Maone wrote: Edit: Using:
Mozilla/5.0 (X11; Linux x86_64; rv:7.0a1) Gecko/20110627 Firefox/7.0a1
and NoScript 2.1.2rc1
Mozilla/5.0 (X11; Linux x86_64; rv:7.0a1) Gecko/20110627 Firefox/7.0a1
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Hi, if it helps, when I said it worked, I was using Firebug 1.7.3 against Firefox 5 (not nightly)Giorgio Maone wrote: Which Firebug version is compatible with Firefox Nightly, exactly?
I just tried it on Firebug 1.8 beta 4 (latest as of writing) against Firefox 5 and that combination did not work either.
This is what I did:
1) In NoScript, I allow localhost
2) I load a page from localhost (firebug closed/not active)
3) I open firebug and in the firebug command line I type in "window" and press return
4) I see the window object appear in firebug console output
5) I reload the page leaving firebug active
6) Repeat step 3 and you get 4.
All good.
Now, I install Firebug 1.8 beta 4 and repeat the above steps.
For step 4, instead of seeing the window object appear in the firebug console output I just see the string "window" echoed but not window object. Same after step 5 and 6.
Hope that helps.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
- Giorgio Maone
- Site Admin
- Posts: 9524
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Cork wrote: Firebug 1.8b => http://getfirebug.com/releases/firebug/1.8/
Code: Select all
<version>1.8.0b4</version>
<targetApplication>
<r:Description>
<id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</id>
<minVersion>3.6</minVersion>
<maxVersion>5.0.*</maxVersion>
<updateLink>https://getfirebug.com/releases/firebug/1.8/firebug-1.8.0b4.xpi</updateLink>
<updateInfoURL>http://getfirebug.com/updateInfo/firebug1.8.xml</updateInfoURL>
</r:Description>
</targetApplication>
Mozilla/5.0 (Windows NT 5.2; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Hi,Giorgio Maone wrote: @anup: did you already tried without NoScript? Do the Firebug guys have anything to say about this (which looks like a separate issue)?
I've tried both versions of Firebug with and without NoScript, and also with NoScript installed and enabled/disabled from the Firefox Addons page.
In terms of what the Firebug guys say, I've been commenting on this thread:
http://code.google.com/p/fbug/issues/detail?id=4333
(My last comment there was about it working but in my haste forgot to state it was 1.7.3 of Firebug for which the problem seems to have gone away. Maybe you can add more info there if needed?)
Hope that helps.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
-
- Posts: 6
- Joined: Fri May 27, 2011 10:56 am
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Just a quick follow-up: This looks to be resolved for me with latest releases:
MacOS X 10.6.8, Firefox 5.0, Firebug 1.7.3, NoScript 2.1.1.2
hoorah!
MacOS X 10.6.8, Firefox 5.0, Firebug 1.7.3, NoScript 2.1.1.2
hoorah!
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20100101 Firefox/5.0
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
console.log() doesn't work, with Firefox Aurora 13.0a2 (2012-03-28), FireBug 1.9.1 and NoScript 2.3.5.
Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120328 Firefox/13.0a2