I think Morgan's referring to the Firebug UI when he says "Console". Similar to the way the UI drops when refreshing or navigating to a new page in 1.4.
On Jul 20, 1:37 pm, johnjbarton <[email protected]> wrote: > Someone sent me email about my post, so let me be more explicit: > > When I type "about:jetpack" into my browser it pops up an alert box: > "The URL is not valid and cannot be loaded". > > Firebug is not designed to debug these internal Firefox messages. > Chromebug can deal with them. > > I still don't understand how this has anything to do with the Console. > (You do mean the Firebug Console panel, not some other console?). > > jjb > > On Jul 19, 8:32 pm, johnjbarton <[email protected]> wrote: > > > I would not expect Firebug to work forjetpack. The about:* things are > > not web pages anyway, at least as far as mozilla's nsIURI is > > concerned. > > > jjb > > > On Jul 19, 12:34 pm, "Morgan 'ARR!' Allen" <[email protected]> > > wrote: > > > > First sentence of the fifth line. > > > *Console will not stay open.* > > > Repeated on the next line > > > *Console closes* > > > I have figured out the problem anyhow. > > > > on line 3446 of firebug.js > > > var host = shortURI.host; > > > .host isn't defined for "about:jetpack", or I'd guess about:anything > > > based on the if(url == "about:blank") exception. > > > I have presented the temporary workaround to just disable "Same Origin > > > on URLs" for people debuggingJetpackfeatures. > > > Long term, maybe adding && uri.host to the if on line 3442 > > > > On Jul 19, 4:45 pm, johnjbarton <[email protected]> wrote: > > > > > Morgan, I can't actually figure out what your problem is from your > > > > post. > > > > jjb > > > > > On Jul 19, 4:20 am, "Morgan 'ARR!' Allen" <[email protected]> > > > > wrote: > > > > > > 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 aJetpackissues, 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 -~----------~----~----~----~------~----~------~--~---
