Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#15681 closed defect (fixed)

the dojo/loadInit plugin improperly assumes a single dojo/_base/loader module

Reported by: Rawld Gill Owned by: Rawld Gill
Priority: low Milestone: 1.8
Component: Loader Version: 1.7.3
Keywords: Cc:
Blocked By: Blocking:

Description

When dojo is mapped, it is possible to have multiple dojo/_base/loader modules. Among other things, dojo/_base/loader implements the dojo/require and dojo/loadInit plugins.

The design of dojo/require assumes a single, page-wide dojo/require plugin instance; there may be many dojo/loadInit instances (each mapped to a different package name). The dojo/loadInit plugin improperly uses dojo/require variables closed by the factory, thereby assuming a particular dojo/require in the same module as a particular dojo/loadInit! is the authoritative instance...which is may not be.

Change History (2)

comment:1 Changed 10 years ago by Rawld Gill

Owner: set to Rawld Gill
Resolution: → fixed
Status: new → closed

In [29248]:

fix dojo/loadInit to not use dojo/require private variables; fixes #15681; !strict

comment:2 Changed 10 years ago by Rawld Gill

Component: General → Loader
Milestone: tbd → 1.8
Priority: undecided → low
Note: See TracTickets for help on using tickets.