Page 1 of 2
Nasty Firebug's console.log() issue with NoScript 2.1.0.1
Posted: Fri Apr 01, 2011 1:59 pm
by Panajev
On the WebGL test apps I am working on, the console.log() function does not print anything* to Firebug's console anymore since the latest update for NoScript got installed. If I disable NoScript and restart the apps, they both print the log correctly.
*Note: console.log(); does not seem to display anything but GET's intercepted by Firebug do show up on the console.
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Posted: Fri Apr 01, 2011 3:02 pm
by Giorgio Maone
Panajev wrote:since the latest update for NoScript got installed.
Does this imply that
downgrading actually cures the symptom?
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Posted: Fri Apr 01, 2011 3:07 pm
by Panajev
Giorgio Maone wrote:[quote="Panajev"since the latest update for NoScript got installed.
Does this imply that
downgrading actually cures the symptom?[/quote]
Well... arg... did not try to downgrade it (I did not even think of doing that since it worked yesterday before the NoScript update and it did not work today just after I restarted Firefox with the NoScript update applied)
...
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Posted: Fri Apr 01, 2011 3:11 pm
by Panajev
Ok, yes... it does imply that
.
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Posted: Fri Apr 01, 2011 3:24 pm
by Giorgio Maone
Is this specific to your app or a simple HTML page with a console.log() statement shows the same issue?
Does the Error Console display any error message?
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Posted: Fri Apr 01, 2011 4:26 pm
by Panajev
I see this:
Code: Select all
Error: [Exception... "Component returned failure code: 0x805e0006 [nsIDOMLocation.href]" nsresult: "0x805e0006 (<unknown>)" location: "JS frame :: chrome://noscript/content/ScriptSurrogate.js :: <TOP_LEVEL> :: line 203" data: no]
Source File: chrome://noscript/content/ScriptSurrogate.js
Line: 203
Edit:
even this page shows the same issue:
Code: Select all
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>t</title>
<meta name="generator" content="Studio 3 http://aptana.com/">
<meta name="author" content="Goffredo Marocchi">
<!-- Date: 2011-04-01 -->
</head>
<body>
<script type="text/javascript">
console.log("...........................");
</script>
</body>
</html>
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Posted: Fri Apr 01, 2011 5:21 pm
by Giorgio Maone
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Posted: Fri Apr 01, 2011 6:00 pm
by Panajev
The only error I get with this development version, that might be related to that (or maybe not), is this:
Code: Select all
Error: this.childNodes[i].tab is undefined
Source File: chrome://browser/content/tabbrowser.xml
Line: 3599
but I still get the same logging problem as before.
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Posted: Mon Apr 04, 2011 8:30 am
by Panajev
Do you have any update on this issue? Firebug is not really usable in this state...
...
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Posted: Tue Apr 12, 2011 7:12 am
by Panajev
Upgraded to the latest NoScript release and I still see this issue.
Boot Firefox, open tab, load webpage, see output in the web console only but no Firebug log anymore. This did not happen with that previous NoScript release as I mentioned before.
Do you have any update on this issue?
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Posted: Tue Apr 12, 2011 11:11 am
by wieseldiesel
Hi @ All,
I have exactly the same Problem! Your FAQ says that noscript.forbidData set to true in about:config helps but not for me!
http://noscript.net/faq#qa3_14
But it seems to be the same Problem because i get a <system> message in Firebug with linkage to a funktion named "httpRequestObserver".
Deleting Firefox & Reinstall it with no Add-Ons but NoScript and new Firefox Profile not help. Is is since last week i guess from the latest update of NoScript.
Thanks GreG
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Posted: Thu Apr 14, 2011 6:36 pm
by netherous
I think I am having the same issue. console.log and all console.x commands produce no output after upgrading to NoScript 2.1.
Steps to reproduce:
1) Load Firefox 4.0 with Firebug 1.7 or later and NoScript 2.1 or later.
2) Go to google.com
3) Type console.log('hi'); into the command box and run it
4) Both the expression evaluated and the resulting output are printed
5) Hit F5 to reload the page
6) Type console.log('hi'); into the command box and run it
7 Only the expression evaluated statement is printed. No output is generated from the invocation of console.log
Alternatively, loading javascript with any console.x from any page also produces no output at any time. Once the console is "broken" in this manner, it can be temporarily fixed by selecting Deactivate Firebug for this Website, and then clicking the bug icon to activate it again. Console output from commands entered into the command box will work until the page is refreshed. Other events, like GET requests, appear in Firebug's log normally even when the problem with the console is occurring.
This happens with Firebug 1.7 and 1.7.1b1 and Noscript 2.1 and above, including 2.1.0.2rc6. Downgrading to NoScript 2.0.9.9 fixes it. Disabling NoScript also allows the console to work normally in Firebug.
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Posted: Fri May 06, 2011 8:57 pm
by azoc
Same issue here. Firebug console does nothing on page load with NoScript 2.1 installed. I was able to get it to work, though impractically, by deactivating Firebug, then reactivating it for the page. At that point I could actually evaluate JS in the console but it was a real pain.
Found this thread and downgraded to 2.0.9.9, now the console works fine as before.
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Posted: Thu May 19, 2011 6:55 am
by Cork
This happens with any output in the console, not just console.log. even just a simple string "test" results in nothing.
Re: Nasty Firebug's console.log() issue with NoScript 2.1.0.
Posted: Fri May 27, 2011 11:01 am
by danielnashnz
Also seen on MacOSX 10.6.7, Firefox 4.0.1, NoScript 2.1.0.5, Firebug 1.7.1 visiting various sites, including
http://www.nature.com
Disabling Noscript got Firebug working again for me.
dunno if this is useful:
Switching NoScript to block the site got me:
Firebug cannot find firebug-CommandLineAttached document.getUserData , its too early for command line Window [
www.nature.com]
[Edit] - Retested with 2.0.9.9 - works fine, 2.1.0 - same issue as described.
Rolling back for now...