I was able to make a quick fix to this issue with dojo and chrome version 29 using the suggestion given in this forum: http://productforums.google.com/forum/#!topic/chrome/wPXjwJ_Kf3M Steps I took: -Download just the query.js from dojo 1.6 toolkit: http://download.dojotoolkit.org/release-1.6.0/dojo-release-1.6.0/dojo/_base/query.js -Remove the condition that checks if resource has already been loaded (dojo._hasResource["dojo._base.query"]) -On line 499, edit it so for chrome v29, _noNES is always true: var _noNES = (navigator.userAgent.indexOf('Chrome/29') >= 0) ? true : (typeof getDoc().firstChild.nextElementSibling == "undefined"); -In your HTML, to make it efficient only load this script when the userAgent is chrome v29. So other browsers do not load this script unnecessarily:
<script type="text/javascript">
if (navigator.userAgent.indexOf('Chrome/29') >= 0){
document.write('<script type="text/javascript" src="/path/to/query.js"><\/script>');
}
</script>
This is still inefficient, considering you have to load the query.js file to override ESRI's - but this fix should keep things stable till the problem gets fixed.
... View more