Error in SeaMonkey (MacOS)

[MonkeySee]

Just trying out SeaMonkey 2.0.14 with Noscript and get the following Console error message on each startup of Seamonkey:

Code: Select all

[NoScript] [NoScript] Error initializing new window TypeError: b is null

I've tried various settings variations with no effect. A search here in the forum reveals no matches.

As for possible incompatibilities with other add-ons - I have the same set running on Firefox 3.6.17 with no such error.

Apart from that everything still seems to work fine with no such message upon opening subsequent new windows or tabs.

Any ideas or tips on how to isolate the issue would be appreciated.
Many thanks

[therube]

(Not seeing that here 2.0.14 Windows, wonder if it is something Mac specific?)

[dhouwn]

Heh, reading the title I thought to myself "somebody is seriously still running classic Mac OS?"

[MonkeySee]

Thanks for the feedback - that seems to eliminate a more general problem.

The error is so cryptic that I'm at a complete loss as to the possible cause. Assuming it's an add-on conflict, I guess there's no way around the long elimination process of disabling all other add-ons and relaunching with each in turn...


Oh, and it is MacOS X - not classic - I just left out the X 'cause it seemed obvious to me - sorry.

[MonkeySee]

After disabling all other add-ons and launching Seamonkey with just NoScript active the message still appears.

No use going through the elimination process then of re-enabling each other add-on in turn.

Anyhow, I'm well aware that very few people would still be running Tiger and that hence this issue would not warrant any serious attention.

Although, If anyone running Seamonkey on Leopard / Snow Leopard could check their Console after launching the app and let me know, I'd be most grateful.

[Giorgio Maone]

After disabling all other add-ons and launching Seamonkey with just NoScript active the message still appears.

Please instal latest development build (actually the most likely release candidate, probably due to become stable in hours), which should give us a more verbose error message.

[Guest]

OK, done - and yes more verbose message this time:

Code: Select all

[NoScript] [NoScript] Error initializing new window TypeError: b is null
()@chrome://noscript/content/noscriptOverlay.js:2408
([object Event])@chrome://noscript/content/noscriptOverlay.js:2361

Thanks for taking the time on this issue with an EOL'ed OS version !

[MonkeySee]

Not sure if it is pertinent, but perhaps I should just add that the message is not related to any site being called - as the startup page is set to blank and the error message occurs even when SeaMonkey is launched in offline mode. Also, for clarity, it is logged to the OS Console - that is, besides the entry appearing in the app's built-in console.

[Giorgio Maone]

Could you check latest development build?

[MonkeySee]

Wow, that was it - nailed it. No more error message.

Terrific responsive support. Thanks!

As soon as I am able to - I will donate!
NoScript Rulez!