#482 closed enhancement (fixed)
debugAtAllCosts working with user namespaces
Reported by: | Morris Johns | Owned by: | Alex Russell |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | General | Version: | 0.3 |
Keywords: | debugAtAllCosts custom widget | Cc: | |
Blocked By: | Blocking: |
Description
Patch to fix debugAtAllCosts so it works even if you use registerWidgetPackage() for your own package.
Also added a parameter so you can re-enable the auto-loading of dojo.require'd files (Parameter is an ugly string, but it works!).
Modified so if you use dojo.hostenv.writeIncludes() more than once, it no longer writes a duplicate copy of all the script tags already written (faster loading!).
Added a test file for user defined package with debugging turned on (attached).
I have put the notes about the debugAtAllCosts feature and using inside the attached test page.
Attachments (4)
Change History (6)
Changed 16 years ago by
Attachment: | test_Custom_Widget_Debugging.html added |
---|
Changed 16 years ago by
Attachment: | browser_debug.js added |
---|
Changed file (complete just in case not merged for a while - change made against rev 2556)
comment:1 Changed 16 years ago by
Milestone: | → 0.3release |
---|---|
Resolution: | → fixed |
Status: | new → closed |
OK, this was basically fixed in checkin #3337, although that doesn't allow the modules loaded by dojo.require() in the content panes to be debugged.
Test file - dojo estswidget est_Custom_Widget_Debugging.html