Databases
StackOverflow2013
Postsdbo
POUsing Dojo 1.9, all parsing fails in IE
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing Dojo 1.9, all parsing fails in IE
    text
    copied!<p>So I have a rather large web app that was running Dojo 1.8. Everything works fine in multiple versions of IE and Firefox. I decided to give 1.9 a go and changed my dependency from 1.8 to 1.9. Firefox worked fine with no noticable changes on first run. IE versions 8 and 9, however, both failed to do much of anything at all. All static HTML content (and dynamic jsp content) was fine, and all of the ajax calls to get the required modules seemed to work fine, but the parser acted like it wasn't ever being called. There were no errors, warnings, or anything in the console.</p> <p>I kept playing with my dojo config, which is nothing special:</p> <pre><code>var dojoConfig = { baseUrl: "js/", async: true, has: { "dojo-firebug": true, "dojo-debug-messages": true }, parseOnLoad: false, isDebug: true, tlmSiblingOfDojo: false, packages: [ { name: "dojo", location: "dojo-release-1.9.0/dojo" }, { name: "dijit", location: "dojo-release-1.9.0/dijit" }, { name: "dojox", location: "dojo-release-1.9.0/dojox" } ] }; </code></pre> <p>I found that if I comment out async: true, IE suddenly starts working again. As you can imagine, I really want to have async true. Why is this tripping IE up? I hope I've provided enough info.</p> <p>edit: I invoke the parser by including a script tag at the bottom of the tag for a file called common.js, which looks roughly like this:</p> <pre><code>require([ "dojo/parser", "dojo/ready" ], function(parser, ready){ ready(function(){ parser.parse(); }); }); </code></pre> <p>I've tried swapping out dojo/ready for dojo/domReady! and taking the parser.parse out of the ready(function(){ block too with the same results.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload