I'm running 1.6x.0a16, but have seen this problem since trying out a14. Firebug is running in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 (.NET CLR 3.5.30729), on WinXP
This may have been the cause of my problems with the console dating back to a14. The application I'm working on uses framesets. With fb 1.5, I routinely use the cd function to set the console's scope to the frame where most of the action is. >>> cd(frames.detail) In 1.6.a16, the console echos i ["Current window:", "[object Window]"] Then if I enter >>> 1+2 the console simply echos my input, and not the resulting "3" The trace spits out: commandLine.evaluate with context.stopped:undefined EXCEPTION TypeError: win.document is undefined win.document is undefined Stack: chrome://firebug/content/consoleInjector.js (17) chrome://firebug/content/consoleInjector.js (39) chrome://firebug/content/console.js (140) chrome://firebug/content/commandLine.js (44) chrome://firebug/content/commandLine.js (101) chrome://firebug/content/commandLine.js (71) chrome://firebug/content/commandLine.js (345) chrome://firebug/content/bindings.xml (1532) ed -- 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.
