I think I have tracked this down to the watchTopWindow method in tabWatcher.js Changes from tabBrowser to Firebug.chrome.getCurrentBrowser in the code from around 105 to 114 and 140, 150,179
On Jul 18, 11:53 pm, "Morgan 'ARR!' Allen" <[email protected]> wrote: > Neither of these problem occur before 1.4b5 and 1.5a7 > > On Jul 18, 8:28 pm, "Morgan ARR! Allen" <[email protected]> > wrote: > > > > > Two issues that have recently appeared. Both are present in 1.4 but I > > cannot say when they appeared. 1.5 has been since around a12 or a13 > > not 100% sure. > > Console will not stay open. If I move to another tab or refresh the > > console closes, making it generally useless. > > console.log will only throw errors. > > > console.log(1); does nothing because 1 exists > > console.log(der); only throws 'der is not defined' > > > This second issue is observed from Jetpacks Develop page, so could be > > more a Jetpack issues, not sure yet. I suspect thou it is related to > > the console closing as they appeared at the same time. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
