On Apr 3, 9:20 am, Landon <[email protected]> wrote:
> So you are saying that the recommended way for people to debug ajax
> calls... is extremely untested and probably doesn't work. Great.

I did not say the recommended way is untested. I said the open in new
window is untested. And I said that if you want to monitor pages on
tabs you can't see, open in new window.

The only thing reported as a bug against new window is reloading the
page, which you can't do if you can't see the tab anyway.

>
> The entire reason I use firebug is I need to see things as they happen
> between going to different pages. I can see the point behind the new
> activation model but the implementation is horrible at the moment. I

Ouch that's a bit harsh  ;-)  Really we only have on bug report it's
not that bad.

> personally think that a good mix of the way it used to work and the
> new activation method is what Trevan described above where if I open
> Firebug on a tab it should stay open on that tab until I either close
> firebug, or close the tab.

I have been thinking about Trevan's suggestion. Another one by Steve
Souders is also possible: no per site setting at all. If you open
Firebug it is on for all tabs and pages. If you close it, it is off
for all tabs and pages. EOF.


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