Opened 12 years ago

Closed 10 years ago

#11445 closed defect (wontfix)

Defered loading in Firefox produces: 'console is not defined' error

Reported by: philip Owned by: Rawld Gill
Priority: high Milestone: tbd
Component: Loader Version: 1.4.3
Keywords: Firefox, console, defered loading Cc: [email protected]
Blocked By: Blocking:


I'm using dijit.Editor and everything is loaded on demand. I have a test case I'm attaching that does not run in Firefox. When you click the button it will load the css and javascript and wait for the djConfig.addOnLoad() callback. This error does not occur when I load dojo from Google. This test case has another button to load from Google to show that it loads without error.

When dojo is loaded normally using <link> and <script> tags, no error is reported. Also, I don't see any errors if I run the example in IE.

When this is run in Firefox, firebug reports an error. Make sure your cache is empty before clicking the load local button. You will also need to adjust the path to where dojo is located on your server.

console is not defined http://localhost:8080/trunk/dojo-release-1.4.3/dojo/dojo.js.uncompressed.js Line 639

The stack trace from firebug is:

console is not defined

  • _loadPath() dojo.j...ssed.js (line 639)
  • require() dojo.j...ssed.js (line 971)
  • (?)() dojo.j...ssed.js (line 11223)
  • forEach() dojo.j...ssed.js (line 2326)
  • (?)() dojo.j...ssed.js (line 11222)
  • (?)() dojo.j...ssed.js (line 16)

Attachments (1)

bug_1.html (2.0 KB) - added by philip 12 years ago.
Deferred loading of dojo hits an error in Firefox

Download all attachments as: .zip

Change History (5)

Changed 12 years ago by philip

Attachment: bug_1.html added

Deferred loading of dojo hits an error in Firefox

comment:1 Changed 12 years ago by philip

Update: I found that setting debugAtAllCosts=true in djConfig makes the error go away. The 1.3 release notes talk about a change to debugAtAllCosts. This could be source of the problem.

comment:2 Changed 11 years ago by Chris Mitchell

Owner: anonymous deleted

comment:3 Changed 10 years ago by bill

Component: GeneralLoader
Owner: set to Rawld Gill

This is likely no longer an issue with the new AMD loader.

comment:4 in reply to:  1 Changed 10 years ago by Rawld Gill

Resolution: wontfix
Status: newclosed

Replying to philip:

Hi Philip,

Please reopen this if it is still a problem with trunk (now in beta for 1.8).

Note: See TracTickets for help on using tickets.