noscriptOverlay warnings

[ozar]

Hey, everyone - here's my basic setup:

Firefox 35 (on Linux):
NoScript 2.6.9.10
Adblock Edge 2.1.7 (EasyList, EasyPrivacy, Fanboy's Annoyance List, and a few custom filters)
Element Hiding Helper 1.31

I'm getting lots of noscriptOverlay warnings in the Linux console such as those below (but not in this particular order):

Code: Select all

"noscriptOverlay<.onMenuShowing@Chrome"
"noscript/content/noscriptOverlay"
"WARNING: content window passed to PrivateBrowsingUtils. is WindowPrivate"
"Use isContentWindowPrivate instead (but only for frame scripts)."
"pub_isWindowPrivate@resources://gre/modules/PrivateBrowsingUtils.jsh"
"onpopupshowing@chrome"
"noscriptOverlay<.openPopup@chrome://browser/content/browser.xul"
"onpopupshowing@chrome://browser/content/browser.xul"
"openPopup@chrome://global/content/bindings/popup.xml"

If I disable NoScript, the warnings do stop, but I'm really not sure if the issue is caused by NoScript, AdblockEdge, Firefox, or some conflict between them, or perhaps it's none of the above. This just started happening recently, but I didn't notice if it was right after updating to FF 35, or after a recent NoScript upgrade. I tried dropping back to NoScript 2.6.9.9, but the problem remained. I've tried a full config reset in NoScript, but still getting a flooded console with these warnings.

My efforts to find a solution on the web have failed me thus far, so I'm hoping that one of you can point me in the right direction for a remedy to this matter?

Thank you.

[barbaz]

Confirmed in SeaMonkey, those messages appear when you pull up the NoScript menu.

Looks like it's just Gecko 35 spitting out deprecation warnings, nothing to worry about
(but from the looks of it, I'd guess those messages won't stop happening until NoScript becomes e10s-aware, which likely not to happen until NoScript 3 is released.)

[barbaz]

Adblock Edge 2.1.7 (EasyList, EasyPrivacy,

offtopic: you should be aware of viewtopic.php?f=19&t=20201

[ozar]

Thanks for the replies, barbaz, regarding both matters.

[Giorgio Maone]

BTW, those specific warnings should be gone in latest development build 2.6.9.11rc1, thanks.

[ozar]

Yes sir, that fixed it... thanks, Giorgio!