This sounds like a new feature for FireStarter extension. http://getfirebug.com/wiki/index.php?title=Firebug_Extensions&oldid=5198#Firestarter
As soon as Firebug 1.7 is out I am planning to work on it, see related issues: http://code.google.com/p/fbug/issues/list?can=2&q=label%3Afirestarter&colspec=ID+Type+Status+Owner+Test+Summary&cells=tiles You can append a note into one of them or create a new if your request is different. Honza On Mar 18, 9:43 am, Anders Gissel <[email protected]> wrote: > Hello all, > > first of all, I just LOVE Firebug. It's the sole reason I'm still > hanging around Firefox instead of Chrome these days. ;-) > > However, there's just one feature I'd really love, and which I haven't > seen being discussed in here – being able to disable Firebug for > specific, preconfigured subfolders of a domain, unless told otherwise. > I work almost exclusively with TYPO3, and its backend is accessed > through domain.tld/typo3/ ... now, I'd like to have Firebug running in > the frontend (anything NOT matching "/typo3/"), but in the backend it > makes no sense to keep the debugging features etc. open. > > For those of us using CMS's like TYPO3, with a preconfigured folder > for the administration backend, being able to disable Firebug once-and- > for-all for that specific folder would be fantastic. I have no idea if > this is at all feasible, but now at least it's out there. > > Thanks for all your great work! > > Best regards > A. Gissel > (Danish intarwebs-nerd) -- 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.
