I suppose that’s what if (window[moduleName] == null) is checking
The problem is that window[moduleName] never shows up. On Chrome it does. From: Alex Harui<mailto:[email protected]> Sent: Thursday, April 30, 2020 6:29 AM To: [email protected]<mailto:[email protected]> Subject: Re: Modules in IE Is this js-debug or js-release? Did the deps file load? Did other definitions get created? If js-debug, there should be new definitions showing up in the global/window object. IOW, if the main app didn't have a DataGrid and the module did, the mx.controls.DataGrid should make an appearance as the deps are loaded and evaluated. -Alex On 4/29/20, 8:19 PM, "Yishay Weiss" <[email protected]> wrote: Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers. From: Alex Harui<mailto:[email protected]> Sent: Thursday, April 30, 2020 12:00 AM To: [email protected]<mailto:[email protected]> Subject: Re: Modules in IE This is IE specific? It works in other browers? What does window[modulename] return? On 4/29/20, 1:41 PM, "Yishay Weiss" <[email protected]> wrote: Has anyone seen this work? To me it’s stuck in UIModuleUtils in COMPILE::JS protected function loadDepsHandler():void { // wait for other scripts to load if (window[moduleName] == null) { setTimeout(loadDepsHandler, 250); } else loadHandler(); } Window[moduleName] is never not null.
