In some circumstances the debugger just doesn't kick in. There are still some steps that you can take though. The first thing that I would do is add an alert statement to check that the JS code is indeed running in Firefox as expected ... you would be surprised how often code is not running due to some quirk somewhere else. If the code is running and the debugger statement is not triggering the debugger you will have to just log your variable to the console. This can be very useful because you can dump JS objects in the way that Firebug does. The syntax is simply console.dir(somevar).
On Mar 25, 4:47 pm, Kimtek <[email protected]> wrote: > I'm working in a complex application built w/ javascript and dojo > widgets. I'm a novice and trying to learn. I'm unable to turn on > "djconfig debug:true". I add the debugger statement in an > xxx.javascript file that was invoked upon dojo.parse. The debugger > statement does not cause a stop. If I do this in IE8, the debugger > stops. IE doesn't seem to have the nice DOM and JS object displays > that Firebug has. Any ideas on how to get it to stop? Thanks. -- 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.
