Changes between Initial Version and Version 1 of Ticket #14619


Ignore:
Timestamp:
Jan 14, 2012, 3:04:32 AM (10 years ago)
Author:
bill
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #14619

    • Property Owner set to Rawld Gill
    • Property Priority changed from high to normal
    • Property Component changed from Core to Loader
    • Property Summary changed from Problem loading dojo with IE in async loading mode to Problem with setting dojoConfig.packages, loading dojo with IE in async loading mode
  • Ticket #14619 – Description

    initial v1  
    11Loading dojo in the new (recommended) way for enabling async. loading, e.g. like this (controlled by JSP) doesn't work with IE (with Firefox there are no problems):
    22
    3  ''<script>
     3 {{{
     4<script>
    45 var dojoConfig = { async:<%=async%>, parseOnLoad: true, packages: [
    56        {name: "generic",location: '<%=rootPath%>/modules/generic'},
     
    89 </script>
    910 <script type="text/javascript" src="<%=dojoPath%><%=dojoFile%>">  </script>
    10 ''
     11}}}
    1112
    1213The loading process stops in dojo.js at the first line of "fixupPackageInfo" (Line 472 of dojo.js in the source release):
    1314
    14 ''fixupPackageInfo = function(packageInfo, baseUrl){[[BR]]
     15{{{
     16fixupPackageInfo = function(packageInfo, baseUrl)
    1517
    16         '''     var name = packageInfo.name;'''[[BR]]
     18        var name = packageInfo.name;
     19
    1720
    1821....
    19 }''[[BR]]
     22}
     23}}}
    2024
    2125This is because by some reason it may happen that packageInfo can be null.
     
    2327A quick fix which solves the problem in my application is:
    2428
    25         '''var name = packageInfo?packageInfo.name:null;'''
     29{{{
     30var name = packageInfo?packageInfo.name:null;
     31}}}
     32
    2633
    2734I am aware, that the root cause of the problem may possibly be somewhere else (that would have been to hard to debug).