4 ms·
FF 3.5 with firebug 1.4 here, it works just fine. The whitelist bug (which I don't care for) will be fixed in the next release, no need to freak out about it. N
by freetard 17y ago
FF 3.5 with firebug 1.4 here, it works just fine. The whitelist bug (which I don't care for) will be fixed in the next release, no need to freak out about it. Now relax and go back to work :)
- gruseom 17y agono need to freak out What are you talking about? it works just fine Have you tested it on my code?
- freetard 17y agoMaybe, could you pass me the links to the bugs you filed for bugzilla? Maybe I could help you and fix firebug. If your only problem is the whitelist thing, then yes, it's no big deal.
- gruseom 17y agoI appreciate that. Unfortunately, I don't know of a way to reproduce the bugs without loading my code, and even then they are intermittent. They seem to have to do with larger JS files, as I mentioned. As far as filing bug reports, I've been waiting until we have a released product, because presumably then I can include a URL to the public version. I couldn't care less about the whitelist bug and don't even know what it is. All I want is a reliable console and debugger. Edit: oh, I just remembered another problem (because it just happened): breakpoints or debugger statements that cause the debugger to break, but jump to the completely wrong source location. This happens all the time and nothing seems to help. (The recommendation to create a new FF profile, which appears to be 80% of the advice given on the Firebug discussion group, doesn't fix this.)