Changes between Initial Version and Version 1 of Ticket #14584


Ignore:
Timestamp:
Jan 9, 2012, 9:23:52 PM (8 years ago)
Author:
bill
Comment:

I'm not sure who this should go to, but I guess it's a problem with dojox.layout.ContentPane rather than the loader itself.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #14584

    • Property Cc Rawld Gill added
    • Property Component changed from Core to DojoX Layout
    • Property Summary changed from "first Dojo wins" policy should not throw "defineAlreadyDefined" error to dojox.layout.ContentPane: "first Dojo wins" policy should not throw "defineAlreadyDefined" error
  • Ticket #14584 – Description

    initial v1  
    11Hi,
    2   A html file loaded by dojox.layout.ContentPane might contain <script src=".../dojo.s"/> in it, the "first Dojo wins" policy just ignore this <scirpt>. For many use cases, such ignorance is good because the first dojo still can be used. However, in dojo 1.7.1, a "defineAlreadyDefined" error is thrown and the code in the html file cannot do anything with the error and hence limits the design based on dojo.
     2  A html file loaded by dojox.layout.!ContentPane might contain {{{<script src=".../dojo.js"/>}}} in it, the "first Dojo wins" policy just ignore this <scirpt>. For many use cases, such ignorance is good because the first dojo still can be used. However, in dojo 1.7.1, a "defineAlreadyDefined" error is thrown and the code in the html file cannot do anything with the error and hence limits the design based on dojo.
    33
    44Rice