Go to about:config in firefox 3
set security.file.strict_origin_policy to false and change the value of security.fileuri.origin_policy to 3 (or 4) - the default is 2.

Details for this option are outlined at http://kb.mozillazine.org/Security.fileuri.origin_policy and http://kb.mozillazine.org/Security.fileuri.strict_origin_policy

This is a known bug in Mozilla.

There is a bug in the jsd (the debugging module of the Mozilla engine) dealing with code defined by an eval statement. If the code run by the eval is brought up in the debugger, it is reported as the line of code which executed the eval itself, plus the line offset within the eval. Since Dojo uses xhr + eval to load all code outside of the bootstrap, this is what you will typically see throughout your callstack when attempting to debug Dojo code in Mozilla.

HTTP monitors and debuggers are tools that monitor the HTTP traffic to/from the server; they are essential for ajax debugging.

For Firefox the answer is short, simple, and cannot be understated. http://getfirebug.com

When you install Firefox, you should select the option for DOM inspector. This tool shows you the DOM tree after the dojo widgets have been expanded. It's indespensible.

There are similar tools for IE. We recommend Microsoft's own Developer Toolbar.

Yes. There's an optional flag available called "debugAtAllCosts" that pulls files in the "expensive" way, in order to provide exactly this. It requires that you include one more line in your usage. Here's how you might use it: