I see, it's been modularized. Thanks! Makes sense now.
On Nov 14, 8:22 am, John J Barton <[EMAIL PROTECTED]> wrote:
> In general Firebug comes disabled for console, script and net. More
> below.
>
> On Nov 14, 1:36 am, Tristan <[EMAIL PROTECTED]> wrote:
>
> > Using 1.4.0a4 with Firefox/Minefield 3.1b2pre nightly. Is there a way
> > to "Suspend Firebug" permanently for most sites? The issue is, the
> > "Suspend Firebug" isn't remembered across browser sessions, so it
> > keeps turning on again.
>
> Suspend and disable are different. But the short answer is no.
>
>
>
> > I liked the old Firebug 1.2(?) method of disabling/enabling Firebug
> > for certain sites, but I recognize the flaws in that too. Just
> > remembering the disabled/enabled status would be sufficient for me.
>
> The disable/enable for 1.4 is the same as 1.2.
>
> You could check the Console, Script, and Net net tabs to make sure
> you've not overridden the defaults. They should all say "Disable".
>
>
>
> > That is, unless there's now no disadvantage to leaving it enabled?
>
> There will always be trade offs:
> Console enabled means sites can see you have firebug.
> Console enabled means the console outputs take time.
> Script enabled takes some CPU (much less in 1.4 if you don;t use
> breakpoints)
> Net enabled adds overhead for every net event.
>
> 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
-~----------~----~----~----~------~----~------~--~---
