[FIXED] error message on startup in 2403 nightly

[dbcooper.dk]

Noscript (2.1.0rc5) triggers the following error message on startup (and when clicking on a download button on megaupload):

ASSERT: gBrowser.addProgressListener was called with a second argument, which is not supported. See bug 608628.
Stack Trace:
0:addProgressListener([object Object],136)
1:()
2:([object Event])

https://bugzilla.mozilla.org/show_bug.cgi?id=608628

[dbcooper.dk]

Anyone else here? This has been confirmed at the mozillazine builds forum now.

[mpz]

Confirmed, getting the same error with NS 2.0.7 as well. I really didn't want to update yet to a newer version of NoScript because it's having several problems on youtube and a few other sites where 2.0.7 isn't, but now got no choice.

[Guest]

Same error here running noscript 2.0.9.9 and minefield 03-24-2011.
Please Fix.

[nerotic]

Confirmed with 2403 nightly and 2.0.9

[therube]

See if the latest development build fixes it for you.

[mpz]

See if the latest development build fixes it for you.

Tried out the latest development build and am getting this error when attempting to go into Full Screen:

ASSERT: gBrowser.addProgressListener was called with a second argument, which is not supported. See bug 608628.
Stack Trace:
0:addProgressListener([object Object],511)
1:([object Event])
2:onFullScreen([object Event])

Edit: On further testing this error appears related to the Autohide extension. Even with NoScript disabled I'm still getting it but is not there when Autohide is turned off.

[therube]

Then it appears multiple extensions may be affecting this.
So to test, you should test with NoScript alone. Then if it reappears after adding other extensions back in, then it is some other extension causing the issue.

[mpz]

Originally I was getting two errors, the first one was the same as the error from the first post but that's gone so it looks like it was NoScript-related and has been fixed. Only those with the Autohide extension installed should get the second error.

[icode]

Getting this error too. I have noscript and no other addons.

[Giorgio Maone]

Please don't reply anymore.
The breakage is caused by a sudden change in Firefox's codebase (you're on the bleeding edge, remember?), affects many extensions and has been fixed in NoScript development builds immediately after.

Always using latest development build is recommended for trunk users (why aren't you?), however now it's fixed in 2.1 stable as well.