Opened 14 years ago

Closed 13 years ago

#221 closed defect (worksforme)

setting debugAtAllCosts=true with external widget classes fails

Reported by: mtreiber@… Owned by: anonymous
Priority: high Milestone:
Component: General Version: 0.1
Keywords: Cc:
Blocked By: Blocking:

Description

When debugAtAllCosts is set, a failure occurs when importing external widget classes even with dojo.hostenv.writeIncludes(). This was with the current svn code. dojo and the external widget classes were loaded with the html below:

<script>

djConfig = { isDebug: true, debugAtAllCosts: true

}; </script> <script type="text/javascript" src="static/javascript/dojo/dojo.js"></script> <script type="text/javascript">

dojo.hostenv.setModulePrefix ("scrappaper","../scrappaper"); dojo.require("dojo.widget.*");

dojo.widget.manager.registerWidgetPackage('scrappaper');

dojo.require("scrappaper.testwidget ");

dojo.hostenv.writeIncludes();

</script>

On Firefix 1.5rc3 on OSX 10.4.3 the debug message was:

DEBUG: auto-build-widgets error: [TypeError: dojo.xml.Parse is not a constructor, file: http://localhost:8080/static/javascript/dojo/src/hostenv_browser.js, line: 277]

and in Firefox's javascript console the below error was given:

Error: dojo.widget.manager has no properties Source File: http://localhost:8080/ Line: 23

Removing debugAtAllCosts:true removed the error and the external widget operated properly.

Change History (2)

comment:1 Changed 14 years ago by anonymous

Summary: setting debugAtAllCosts=true with external widget classes failrssetting debugAtAllCosts=true with external widget classes fails

comment:2 Changed 13 years ago by dylan

Resolution: worksforme
Status: newclosed

This is more likely due to an error in the code or the way the external namespace is provided. Please reopen if this is still an issue.

Note: See TracTickets for help on using tickets.