For some strange reason I can't see your message on web, so will reply by mail. General thought: FireBug still works fine, but its behavior is very unclear now.
> - Easy workflow - Enabling a site was a one-time operation and that > was a miniscule amount of effort since sites that I debug are usually > ones that I work on frequently. It's the same one click now: one click on the FB icon in status bar; if you need to activate FB for the site but to leave it collapsed, you'll have to do one more click on the collapse icon in the top-right corner of FB panel (not on the "Off" one!). In the prev. version you had to make two or three clicks anyway. > - Screen real estate - my laptop doesn't have the vertical real estate > to always have the firebug panel open, but I always want the console > running. A separate window doesn't help because I usually need to see If you use the collpase button, not the "Off" one, you'll have the panel collpsed, but FB still running (icon in statusbar will be orange, not gray). > - Error notification - even when I wasn't debugging client-side > things, it was *fantastic* to get the red "error" notification by the > firebug icon (with firebug collapsed) to help me catch bugs early on > and to let me know that something bad had happened. It's still the same, if the console is collapsed, not disabled. > - Bug reproducibility - By always having the console running I have a > backtrace available as soon as I hit a bug and tracking down hard-to- > reproduce bugs is much easier. I haven't checked it especially yet, but the console is running, as I mentioned before, so you should have everything OK. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
