debugAtAllCosts: true makes modules loaded twice

[jfcunat]

When you add debugAtAllCosts true in a djConfig, some modules are loaded twice and it causes some problems. Try dijit/tests/test_ColorPalette.html with IE6 with a non builded Dojo, and add a debug in dojo.provide function, you will see that we go twice in many modules.

It makes a problem with templated Widget because function called by dojo.addOnUnload is executed twice and makes an error the second time. file _Templated.js line 253 It causes a problem on the _destroyElement on IE 6

[bill]

This doesn't need to be fixed for 1.0.1 as there is a simple workaround (don't use debugAtAllCosts: true), but passing on to James to see if he can do anything. I suspect this is just how debugAtAllCosts works though.

[bill]

(In [11493]) Fixes #5060 on 1.0 branch: ColorPalette? inefficient code and memory leak on IE6. Also makes _Templated.js's dojo.addOnUnload() call itempotent since it executes twice when debugAtAllCosts is true (refs #5091).

Thanks to Jean Cunat (Orange-ftgroup CCLA on file) for patch.

[bill]

(In [11494]) Fixes #5060 on trunk: ColorPalette? inefficient code and memory leak on IE6. Also makes _Templated.js's dojo.addOnUnload() call itempotent since it executes twice when debugAtAllCosts is true (refs #5091).

Thanks to Jean Cunat (Orange-ftgroup CCLA on file) for patch.

[jburke]

(In [11910]) Fixes #5091: debugAtAllCosts including files twice in the head.