Page 1 of 1

[Invalid] XSS Notifications Not Being Logged In SeaMonkey

Posted: Sat Apr 05, 2014 9:46 am
by therube
It looks like XSS Notifications are Not Being Logged In SeaMonkey ?

URL: http://www.abelhadigital.com/multihasher

I do get the Yellow warning line in the browser window, I can open Error Console from the NoScript icon (XSS->) or from the warning Option..., but I'm not seeing anything "NoScript" or "XSS" in Error Console.

(It is logged in FF.)

Re: XSS Notifications Not Being Logged In SeaMonkey

Posted: Sat Apr 05, 2014 10:11 am
by Thrawn
Firefox has moved to the Browser Console instead of the Error Console...maybe NS is trying to log there instead? (Does Seamonkey have a Browser Console?)

Re: XSS Notifications Not Being Logged In SeaMonkey

Posted: Sat Apr 05, 2014 3:01 pm
by barbaz
Thrawn wrote:Firefox has moved to the Browser Console instead of the Error Console...maybe NS is trying to log there instead?
That's not it. If you type this in the address bar

Code: Select all

http://0.0.0.0/<script>
NS complains and the related messages are in the Error Console, under Messages...
My guess is that the Error Console is flooded with too many CSS warnings to be able to keep the XSS messages in the list.

(@therube, I'm not seeing any XSS warning at all on that URL... Go there, see nothing, so Temp-Allow the top-level domain, and... still nothing.)
Thrawn wrote:(Does Seamonkey have a Browser Console?)
Sadly not, and it doesn't look possible to add it as an extension either :cry:

Re: XSS Notifications Not Being Logged In SeaMonkey

Posted: Sat Apr 05, 2014 4:14 pm
by therube
OK, I see that.
My guess is that the Error Console is flooded with too many CSS warnings to be able to keep the XSS messages in the list.
That must be it.
I'd clear the Console, open the link in a new tab, & there are a ton of messages. Just didn't expect it to be of such a number that I would loose the wanted XSS message.