Just a quick query. I have written a large web application which has been through unit testing on all major browsers.
No problems in all other broswers, and really no problem in FF unless firebug is enabled. This was never a problem before, ive had firebug open for months prior to the new build.
I was just wondering if anyone has experienced the same?
I have experienced bugs in firebug, which always reminds me that using it must change things. Having it enabled simply has to alter the browser environment and behavior a tiny bit.
I wouldn't be surprised if the broken code relies on time for correctness. Or maybe relied upon something unsuitable for synchronization or mutex purposes. Then again, you could say it was never really correct in the first place.
Since you have reason to believe the click event(or the code to handle the event) is sometimes firing more often than intended, I would examine that area a little closer. It's possible that it's happening whether firebug is enabled or not, but your current method of testing/examining doesn't reveal it, and the effect of it doesn't quite manifest itself all the way to the broken output.
With that said, a lot of bugs I've seen in programs that use ajax are due to reliance on time, and using global variables(or variable who just have too large of a scope).