There are a few cool methods for debugging Javascript in Firebug:
- In addition to everybody's favorite console.log() method, there is also
console.debug(), console.info(), and console.error(), each of which are
color coded differently. If you use console.error(), then it actually logs
it as a Javascript error, even if the syntax is correct.
- console.trace() will give you a detailed stack trace, providing the
funtions on the stack and the values of each argument.
- console.dir(object) will dump all the properties of the passed object
- console.dirxml(element) will elegantly dump any XML element. It doesn't
exist uet, but I'd love a console.dirjson(element) method.
- You can chunk any logging messages by running console.group("Group
title") before and console.groupEnd() after a related group of code. You can
nest as many levels as you'd like.
-
- You can track Javascript performance by running console.profile()
before the code you want to track, then console.profileEnd() afterward.
Firebug will give detailed information on each method called between the
Chuck Harmston
http://chuckharmston.com
On Tue, Apr 7, 2009 at 1:10 AM, rachel navarro <rachelannenava...@gmail.com>
wrote:
> i have a related question. how do i track my code? how do i know which
> function is being called first and so on? like having a stack trace. is
> there such a tool for firefox?
>
> On Tue, Apr 7, 2009 at 6:57 AM, MorningZ <morni...@gmail.com> wrote:
>>
>> "how to debug" is a pretty super vague statement
>>
>> what are you looking to do? find objects? track your code? watch
>> AJAX requests?
>>
>>
>> On Apr 6, 10:50 am, jQueryAddict <jqueryadd...@gmail.com> wrote:
>> > I've seen a crapload of old posts but none really work well. Is
>> > everyone still just using the consol log thingy in Firebug or what?
>> > I've never used that with jQuery so I do not understand how to debug
>> > jQuery in Firebug still
>
