Opened 8 years ago
Closed 7 years ago
#14584 closed defect (fixed)
dojox.layout.ContentPane: "first Dojo wins" policy should not throw "defineAlreadyDefined" error
| Reported by: | riceyeh | Owned by: | Rawld Gill |
|---|---|---|---|
| Priority: | high | Milestone: | 1.8 |
| Component: | DojoX Layout | Version: | 1.7.1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description (last modified by )
Hi,
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.
Rice
Change History (4)
comment:1 Changed 8 years ago by
| Cc: | Rawld Gill added |
|---|---|
| Component: | Core → DojoX Layout |
| Description: | modified (diff) |
| Summary: | "first Dojo wins" policy should not throw "defineAlreadyDefined" error → dojox.layout.ContentPane: "first Dojo wins" policy should not throw "defineAlreadyDefined" error |
comment:2 Changed 8 years ago by
| Cc: | Rawld Gill removed |
|---|---|
| Owner: | set to Rawld Gill |
| Status: | new → assigned |
Similar or dup of #14580?
comment:3 Changed 7 years ago by
| Milestone: | tbd → 1.8 |
|---|
Version 1.8 does not throw.
There is a small abnormality where the second dojo will try to execute deps and callback in the object space defined by a private require which never gets moved to global require. This should be fixed so that trying to load dojo.js twice is effectively a no-op.
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.