I have mixed reviews.  I was a person that used the "enabled everywhere but on 
some sites" setting because I liked to look at how other sites worked every now 
and then.  I think there are actually two uses for firebug:

Looking at CSS and HTML
Using console.log and ajax listening

This new model works great for the CSS and HTML usage.  You can turn on firebug 
on the site you are looking at, check out the css and html, close firebug and 
be done.

But for console.log and ajax listening (especially at page load), it doesn't 
really work.  You have to make sure firebug is open before the page is loaded 
if you want to see any output of the console.log and watch any ajax calls.  And 
since firebug closes itself on every new page, this makes watching stuff on 
page load very frustrating.

Personally, if I have firebug open in a tab, I expect it to stay open in that 
tab until I close it (and for it to be listening for ajax requests and 
console.log calls on that tab.  I don't care if I'm switching domains or 
staying in the same domain, if I opened up, stay open.  Since I'm usually 
debugging more than one page, this new model is becoming very frustrating.  I 
setup the environment, I go through the steps to get the form to submit, I 
submit expecting to check ajax requests and console.log calls on the next page 
and firebug closes.  Completely destroying the possibility to debug.  I've 
started changing console.log to something else and catching ajax requests in 
another way just so I can work.

Another frustrating aspect is that one workaround this issue is to make sure 
firebug has already been opened on each of the pages.  This makes firebug stay 
open when you switch pages.  But when I'm done debugging, I close it and assume 
that it should stay closed.  But firebug only closes it for the page I'm 
currently on.  If I go to one of the other pages, firebug reopens unexpectedly. 
 So I close it.  Another page reopens it, I close it.  And it continues (I've 
usually opened it on 10+ pages in the course of debugging).  And now that I've 
closed it on all those pages, when I want to debug them (for another issue), 
I've got to remember to reopen it on each of those pages (and I only remember 
after being reminded painfully after firebug closes the first couple of times 
on me).

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to