debugAtAllCosts: dojo.provides race conditions

[bill@…]

In browser_debug.js, dojo.hostenv.loadUri calls dojo.provide(), thus creating an empty package, but the package isn't filled in (with functions definitions, etc.) until much later in writeIncludes().

In particular this leads to a problem in event.js, which does a "if(dojo.eventbrowser?)". The code inside the "if" is executed because dojo.event.browser exists, but breaks because dojo.event.browser doesn't contain the expected functions.

Try loading test_fisheyewidget.html while moving your mouse over the screen (near where the icons are displayed) and then look in the javascript console to see the problem.

[Tom Trenka]

Bill, is this still an issue?

[bill]

Yeah. If you change debugAtAllCosts to true in test_fisheyeWidget.html and then move your mouse during page load there will be dozens of errors. (On the other hand, there are sometimes errors even when debugAtAllCosts is false)

[James Burke]

This should be fixed in 1.0, since debugAtAllCosts does not depend on writeIncludes() now and uses the xdomain loading mechanism.