Hey Guys, I am a long time users of Firebug - in the dark ages before I found it I had major troubles figuring out which CSS rule applied to what element(s), creating solutions without having to constantly save- reload a local file (or even worse, a remote one), etc.
Firebug is one of my essential tools for any web development work. But I do have a slight problem, specifically when I am using the console.X( ... ) functionality to help me trace and debug javascript activity. The problem is when other people view the files which I am debugging, in a browser which does not support console, or has limited support for console (and so doesn't have console.groupCollapsed(), for instance) they get javascript errors and the whole thing just falls apart. I know that some HTML frameworks include a bit of javascript which identifies users visiting with browsers which do not handle console calls, (and have made some homebrew javascript for the same purpose on occasion), but I wanted to offer a suggestion which, as a developer, I would find immensely helpful. If Firebug added "Firebug" to the User Agent of the browser, it would allow for server-side scripting to identify whether the browser would handle console messages, and, then conditionally include/exclude that content from served pages. I know that FirePHP does this, and that I could use a similar check for that string (although I would not find users who had Firebug, but not FirePHP). Even if the User Agent tweak could just be a function users could optionally toggle on and off (again, like FirePHP) this would be a terrific addition to an already brilliant system. Cheers, Luke -- 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.
