I like it to my mind it makes sense. The only thing I can see being a problem is the debugger being hit and the active tab not switching to the script tab (which happens a lot), this usually (only?) occurs when your current selection is the HTML tab but at least you can see the debugging buttons being turned on so you navigate to the script tab and start working away. Of course if the buttons are no longer visible this may lead to some weird confusion...
It's clear that Firebug cannot actually stop the JS engine in Firefox which is a pity because as I'm debugging I can see the application merrily working away and therefore cannot really see which piece of JS has what effect on the app. On Wed, Feb 18, 2009 at 6:08 AM, John J Barton <[email protected]>wrote: > > Curtis Bartley has a prototype XPI of Firebug with the panel tabs > moved to the top of the Firebug UI and the toolbar beneath it. We are > considering whether to include this in 1.4 release. Your input is > welcomed. We are especially interested in potential but unexpected UI > problems this change may cause. > > http://curtisb.posterous.com/improving-the-firebug-ui > > jjb > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
