Disabling Firebug per site

[MosheC]

Hi,
In old Firebug it was very simple to disable Firebug per site.

In the new version it all seems so complicated.
In different tabs I can disable only one aspect of Firebug.

How do I achieve the task of disabling Firebug completely per site?

Moshe

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@...
To unsubscribe from this group, send email to firebug-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---

[John J Barton]

There are three ways to disable Firebug per site.

1) Do nothing. Firebug is disabled by default.
2) Open Firebug on the site, disable each of Console/Script/Net by
using small menus on these panel tabs.
3) Open Firebug on any site, use the small menus "Site" entry to
disable by text.

However, many people have unrealizable expectations for disable by
site.  It only filters out the site for output, it does not prevent
Firebug from operating when you are viewing the site.

If the Firebug icon is orange, Firebug is active.

John.

On Jul 23, 5:50 am, "Moshe C." <mos...@...> wrote:
> Hi,
> In old Firebug it was very simple to disable Firebug per site.
>
> In the new version it all seems so complicated.
> In different tabs I can disable only one aspect of Firebug.
>
> How do I achieve the task of disabling Firebug completely per site?
>
> Moshe
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@...
To unsubscribe from this group, send email to firebug-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---

[MosheC]

Thanks.

Point (1) seems to contradict your final note.

Wasn't that possible in the old version, i.e. completely disabling per site?

On Wed, Jul 23, 2008 at 6:01 PM, John J Barton <johnjbarton@...> wrote:

There are three ways to disable Firebug per site.

1) Do nothing. Firebug is disabled by default.
2) Open Firebug on the site, disable each of Console/Script/Net by
using small menus on these panel tabs.
3) Open Firebug on any site, use the small menus "Site" entry to
disable by text.

However, many people have unrealizable expectations for disable by
site.  It only filters out the site for output, it does not prevent
Firebug from operating when you are viewing the site.

If the Firebug icon is orange, Firebug is active.

John.

On Jul 23, 5:50 am, "Moshe C." <mos...@...> wrote:
> Hi,
> In old Firebug it was very simple to disable Firebug per site.
>
> In the new version it all seems so complicated.
> In different tabs I can disable only one aspect of Firebug.
>
> How do I achieve the task of disabling Firebug completely per site?
>
> Moshe

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@...
To unsubscribe from this group, send email to firebug-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---

[John J Barton]

On Jul 23, 8:13 am, "Moshe Cohen" <mos...@...> wrote:
> Thanks.
>
> Point (1) seems to contradict your final note.

Point 1 is that, unlike Firebug 1.0 and 1.1, if you don't enable one
of the three panels on some page in some tab, then Firebug 1.2 has no
almost no overhead (one or two on-load handlers for tabs so it can
know if you want to activate it).

>
> Wasn't that possible in the old version, i.e. completely disabling per site?

No, it isn't technically possible. The interface between Firebug and
Firefox is not controlled on a per-page basis.

>
> On Wed, Jul 23, 2008 at 6:01 PM, John J Barton <johnjbar...@...>
> wrote:
>
>
>
> > There are three ways to disable Firebug per site.
>
> > 1) Do nothing. Firebug is disabled by default.
> > 2) Open Firebug on the site, disable each of Console/Script/Net by
> > using small menus on these panel tabs.
> > 3) Open Firebug on any site, use the small menus "Site" entry to
> > disable by text.
>
> > However, many people have unrealizable expectations for disable by
> > site.  It only filters out the site for output, it does not prevent
> > Firebug from operating when you are viewing the site.
>
> > If the Firebug icon is orange, Firebug is active.
>
> > John.
>
> > On Jul 23, 5:50 am, "Moshe C." <mos...@...> wrote:
> > > Hi,
> > > In old Firebug it was very simple to disable Firebug per site.
>
> > > In the new version it all seems so complicated.
> > > In different tabs I can disable only one aspect of Firebug.
>
> > > How do I achieve the task of disabling Firebug completely per site?
>
> > > Moshe

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@...
To unsubscribe from this group, send email to firebug-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---

[Brian Williams]

Ok... so what you are saying is that the interface ( in firefox 3, between it and firebug [current version]) has changed and can no longer be active/inactive on a per tab/domain basis? 

To get around that change (ignoring who made that interface change) you have made the "disabled" feature on a per domain basis actually cause firebug to not provide output for that domain?  But Firebug is still running... i.e. it will still cause problems (pop up alerts saying something along the line of (this script has stopped working click stop, debug, or continue) if there is a bug somewhere that's not handled correctly?  (yes i have seen this and can sort of reproduce it in some work i am doing -- when i say sort of i mean, it happens when I'm not actually developing javascript but the page is using some javascript)

if that is the case, can you also provide a per sub-domain filtering?

i.e. i have mysite.com where i want firebug to work, but I don't necessarily want firebug on all the time for development.mysite.com

please correct me if i am wrong.

thanks

On Wed, Jul 23, 2008 at 11:35 AM, John J Barton <johnjbarton@...> wrote:

On Jul 23, 8:13 am, "Moshe Cohen" <mos...@...> wrote:
> Thanks.
>
> Point (1) seems to contradict your final note.

Point 1 is that, unlike Firebug 1.0 and 1.1, if you don't enable one
of the three panels on some page in some tab, then Firebug 1.2 has no
almost no overhead (one or two on-load handlers for tabs so it can
know if you want to activate it).

>
> Wasn't that possible in the old version, i.e. completely disabling per site?

No, it isn't technically possible. The interface between Firebug and
Firefox is not controlled on a per-page basis.

>
> On Wed, Jul 23, 2008 at 6:01 PM, John J Barton <johnjbar...@...>

> wrote:
>
>
>
> > There are three ways to disable Firebug per site.
>
> > 1) Do nothing. Firebug is disabled by default.
> > 2) Open Firebug on the site, disable each of Console/Script/Net by
> > using small menus on these panel tabs.
> > 3) Open Firebug on any site, use the small menus "Site" entry to
> > disable by text.
>
> > However, many people have unrealizable expectations for disable by
> > site.  It only filters out the site for output, it does not prevent
> > Firebug from operating when you are viewing the site.
>
> > If the Firebug icon is orange, Firebug is active.
>
> > John.
>
> > On Jul 23, 5:50 am, "Moshe C." <mos...@...> wrote:
> > > Hi,
> > > In old Firebug it was very simple to disable Firebug per site.
>
> > > In the new version it all seems so complicated.
> > > In different tabs I can disable only one aspect of Firebug.
>
> > > How do I achieve the task of disabling Firebug completely per site?
>
> > > Moshe

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@...
To unsubscribe from this group, send email to firebug-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---

[John J Barton]

On Jul 23, 8:46 am, "Brian Williams" <brianw1...@...> wrote:
> Ok... so what you are saying is that the interface ( in firefox 3, between
> it and firebug [current version]) has changed and can no longer be
> active/inactive on a per tab/domain basis?

No, I am not saying that. The interface did not change. The biggest
change since Firebug 1.0 has been on the Web: much more AJAX.

>
> To get around that change (ignoring who made that interface change) you have
> made the "disabled" feature on a per domain basis actually cause firebug to
> not provide output for that domain?  But Firebug is still running... i.e. it
> will still cause problems (pop up alerts saying something along the line of
> (this script has stopped working click stop, debug, or continue) if there is
> a bug somewhere that's not handled correctly?  (yes i have seen this and can
> sort of reproduce it in some work i am doing -- when i say sort of i mean,
> it happens when I'm not actually developing javascript but the page is using
> some javascript)
>
> if that is the case, can you also provide a per sub-domain filtering?
>
> i.e. i have mysite.com where i want firebug to work, but I don't necessarily
> want firebug on all the time for development.mysite.com
>
> please correct me if i am wrong.
>
> thanks
>
> On Wed, Jul 23, 2008 at 11:35 AM, John J Barton <johnjbar...@...>
> wrote:
>
>
>
> > On Jul 23, 8:13 am, "Moshe Cohen" <mos...@...> wrote:
> > > Thanks.
>
> > > Point (1) seems to contradict your final note.
>
> > Point 1 is that, unlike Firebug 1.0 and 1.1, if you don't enable one
> > of the three panels on some page in some tab, then Firebug 1.2 has no
> > almost no overhead (one or two on-load handlers for tabs so it can
> > know if you want to activate it).
>
> > > Wasn't that possible in the old version, i.e. completely disabling per
> > site?
>
> > No, it isn't technically possible. The interface between Firebug and
> > Firefox is not controlled on a per-page basis.
>
> > > On Wed, Jul 23, 2008 at 6:01 PM, John J Barton <
> > johnjbar...@...>
> > > wrote:
>
> > > > There are three ways to disable Firebug per site.
>
> > > > 1) Do nothing. Firebug is disabled by default.
> > > > 2) Open Firebug on the site, disable each of Console/Script/Net by
> > > > using small menus on these panel tabs.
> > > > 3) Open Firebug on any site, use the small menus "Site" entry to
> > > > disable by text.
>
> > > > However, many people have unrealizable expectations for disable by
> > > > site.  It only filters out the site for output, it does not prevent
> > > > Firebug from operating when you are viewing the site.
>
> > > > If the Firebug icon is orange, Firebug is active.
>
> > > > John.
>
> > > > On Jul 23, 5:50 am, "Moshe C." <mos...@...> wrote:
> > > > > Hi,
> > > > > In old Firebug it was very simple to disable Firebug per site.
>
> > > > > In the new version it all seems so complicated.
> > > > > In different tabs I can disable only one aspect of Firebug.
>
> > > > > How do I achieve the task of disabling Firebug completely per site?
>
> > > > > Moshe

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@...
To unsubscribe from this group, send email to firebug-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---