On Wednesday, December 28, 2011 11:17:51 PM UTC+1, Andrew Whitfield wrote: > > I've noticed that pressing F12 brings up Firebug like normal but doesn't > load the console properly. You have to press F12 twice to bring up the > console. Causing deliberate JavaScript errors doesn't cause errors to show > up in the console either. I think there's something in the latest update > that's tripping up the console itself. > I am not sure if I understand the problem, what exactly should I do to see it?
Here is what I am trying: 1) Load http://getfirebug.com/tests/content/branches/1.9/console/872/main.html 2) Press F12 to activate Firebug (opens Firebug UI) 3) Select and Enable the Console panel 4) Refresh the page 5) The console panel is displaying an error log: "This is an error from an iframe!" > > I'm on Windows 7 as well. > > The firebug options button (which appears on the row to the left of the > element select button) doesn't trigger the menu to open like it did in > previous versions. > This seems to be working for me. Do you see any errors in Firefox error Console? > Anything I can do to help you with these? > Regarding to the Console panel problem: Please provide a test page with detailed steps-to-reproduce Regarding to the option menu: Do you see any errors if you install Firebug Tracing Console and check the ERRORS option? http://getfirebug.com/releases/fbtrace/1.9/fbTrace-1.9b4.xpi Honza > Kindest thanks for an amazing creation. > > Andrew > -- 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 https://groups.google.com/forum/#!forum/firebug
