The console object it supposed to be available before any JS code executes. If it is not, its a bug and we'd like a test case so we can solve it. jjb
On Apr 17, 7:17 am, Garrett LeSage <[email protected]> wrote: > It seems that firebugx.js and firebug-lite.js are not compatible with > the recent alphas of Firebug. This happened a few alpha versions ago, > and I believe it is with the new-new activation of Firebug. > > The symptoms are: > > 1) Firebug closing on page reloads > 2) Both Firebug and Firebug lite pop up at the same time (when > including Firebug lite) > > As you can guess, it's quite an annoying behavior. > > I'm guessing that it's because the method used for detecting Firebug > (checking for console) fails, as Firebug does not add the console > object until after the page's code has been executed. Of course, I > could be completely wrong, too. (: > > (For now, I've just removed the include in development mode.) > > Is there a better way of determining if Firebug is (or is not) > present? or is this a bug in the recent versions of Firebug? > > Garrett --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
