"Syncing..." console log spamming

[codecodecode]

Windows 7 Ultimate x64
Firefox 41.0.1
NoScript 2.6.9.37

Massive console log spamming, feature??

noscriptOverlay.js

Code: Select all

   try {
     if (w && w.QueryInterface(Ci.nsIInterfaceRequestor)
                      .getInterface(Ci.nsIDOMWindowUtils).currentInnerWinowID
           != content.QueryInterface(Ci.nsIInterfaceRequestor)
                      .getInterface(Ci.nsIDOMWindowUtils).currentInnerWinowID)
      return;
     console.log("Syncing...");  // here ****
   } catch (e) {
     console.log(e);
   }

https://i.imgur.com/PyvW8Js.png

[barbaz]

Massive console log spamming, feature??

Can't speak for Giorgio but I very much doubt it. It's probably debugging code (which may or may not unintentionally left there), but perhaps the reason you see it is because there's two small typos in the code you posted?

try {
if (w && w.QueryInterface(Ci.nsIInterfaceRequestor)
.getInterface(Ci.nsIDOMWindowUtils).currentInnerWinowID
!= content.QueryInterface(Ci.nsIInterfaceRequestor)
.getInterface(Ci.nsIDOMWindowUtils).currentInnerWinowID)
return;
console.log("Syncing..."); // here ****
} catch (e) {
console.log(e);
}

(I don't understand why am I not seeing that in SeaMonkey's Error Console?)

[codecodecode]

Can't speak for Giorgio but I very much doubt it. It's probably debugging code (which may or may not unintentionally left there), but perhaps the reason you see it is because there's two small typos in the code you posted?

That's the "official" "signed" code (god f*cking bless mozilla) form v2.6.9.37 [https://addons.mozilla.org/en-US/firefo ... pt.ownsite]

[barbaz]

And your point is...?
I'm just saying that it might be that that should say "Window" and not "Winow". What has this to do with whether or not it's the "official" signed code?

(It's like that in my NoScript 2.6.9.37rc2 also)

[Giorgio Maone]

Yes it's a bug (which has no side effect but the console spamming), and is gonna be fixed in next build.

[codecodecode]

And your point is...?

The point is that if I want to fix the error today I can do it by myself but when extension signing becomes mandatory I can't do it, that's all.

Yes it's a bug (which has no side effect but the console spamming), and is gonna be fixed in next build.

Thanks.

[barbaz]

The point is that if I want to fix the error today I can do it by myself but when extension signing becomes mandatory I can't do it, that's all.

Ah, OK. There will be (or at least, it's planned to be) unbranded builds of Firefox, with extension signing enforcement not mandatory, at that point...