You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Yishay Weiss <yi...@hotmail.com> on 2020/05/02 18:01:24 UTC
RE: Modules in IE
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
Re: Modules in IE
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Alex,
Would it tells you more if Yishay share with you compiled code ?
Thanks,
Piotr
niedz., 3 maj 2020 o 08:31 Alex Harui <ah...@adobe.com.invalid> napisał(a):
> I just ran examples/royale/ModuleExample in IE and it worked. Does it
> work for you?
> In the debugger, window.Module and window.MainApp resolve to functions.
> window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in the head.
> Near the end of the list should be the script for the .js file for the
> module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <yi...@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF. window[this.modulename] is
> undefined. Didn’t check what happens in other browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <yi...@hotmail.com>
> 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.
>
>
>
>
>
>
>
>
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Modules in IE
Posted by Alex Harui <ah...@adobe.com.INVALID>.
You can try it by manually adding the JS to the beginning of the module's .js file. There are already places in Royale where we createElement('script') and createElement('link'). Royale essentially runs JS to generate the equivalent of html tags.
HTH,
-Alex
On 5/11/20, 10:00 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>What if we abandon "inject_html" and go with "inject_script" instead? Then when adding to the html output, each >script would be wrapped with a <script> tag, but for modules the code could be added to the main module .js file.
I’m not sure about this. I think typically you inject a <link href=”x”> for css and a <script src=”y”> for the js. How do you propose to add those to the module js?
On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
Hi Carlos, thanks. The issue is with inject_html in modules on IE, dialogPolyfill.js just happened to be the target src here. I’ve been searching the net for solutions on IE and I think the trick is to append elements instead of changing the inner html. I see two options of transpiling <inject_html> that would work on IE:
1. Parse the <inject_html> contents in the compiler and create js that would work for IE. Difficult.
2. Replace each line in <inject_html> with dummy elements and change their outerHTML to match each line contents. This one looks easier, but I seem to remember a thread where we were trying to eliminate use of outerHTML.
Any thoughts are welcome.
From: Carlos Rovira<ma...@apache.org>
Sent: Monday, May 11, 2020 6:06 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: Modules in IE
Hi Yishay,
talking without a huge analisys of the problem. I think Jewel Alert works
ok in IE11 so that should mean dialogpolyfil is loading ok. if not the case
something broke recently since I checked that in TDJ and other apps we did.
Anyway, the commit you state is just to give the support we needed. I
didn't tested in IE11, so don't know if we support it. Normally IE11 use to
require
some special way of writing the code for some particular things, so I think
the way to solve this is:
1.- search in SOF or other sources how IE11 expect scripts to be added
dynamically
2.- upgrade the compiler code to use that way with that considerations to
make it IE11 compatible and check if that works for IE11 and rest of
browsers.
sorry to not be able to say much more, but I'm these days with few time
Thanks
El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<yi...@hotmail.com>)
escribió:
> Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in compiler code
> doesn’t work for IE11. Any ideas on how to fix this?
>
> From: Yishay Weiss<ma...@hotmail.com>
> Sent: Monday, May 11, 2020 4:52 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: RE: Modules in IE
>
> These lines in dialogPolyfill.as
>
> * <inject_html>
> * <script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C2d00ea036378467d3da508d7f5ccd652%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248132431130649&sdata=zwnqSP6W3Tqm8GTWHHxr5SzEf%2BfqTM1%2FadjkD0O1G6M%3D&reserved=0
> "></script>
>
> get transpiled to
>
> document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C2d00ea036378467d3da508d7f5ccd652%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248132431130649&sdata=zwnqSP6W3Tqm8GTWHHxr5SzEf%2BfqTM1%2FadjkD0O1G6M%3D&reserved=0
> "></script>'
>
> But that’s making IE11 fail in loading the module. It doesn’t matter what
> the src is, IE will silently fail. For example, I’m getting the same result
> if I replace the above with
>
> document.head.innerHTML += '<script></script>'
>
>
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:35:55 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C2d00ea036378467d3da508d7f5ccd652%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248132431140642&sdata=4e7msxtlmO2lim1%2BFh8%2BIck%2FlPjr%2BRzmzQqUD7irWzs%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C2d00ea036378467d3da508d7f5ccd652%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248132431140642&sdata=4e7msxtlmO2lim1%2BFh8%2BIck%2FlPjr%2BRzmzQqUD7irWzs%3D&reserved=0
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C2d00ea036378467d3da508d7f5ccd652%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248132431140642&sdata=ddTEKth7I0HiTePSjA8KUEBLrhijnvdcdcEKz6YMq8Q%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C2d00ea036378467d3da508d7f5ccd652%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248132431140642&sdata=Q%2BCIVUtZmPqgd%2F0y5W7hUN5Q6Qf2IXXXmkrjSF8AKlI%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:36 PM
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C2d00ea036378467d3da508d7f5ccd652%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248132431140642&sdata=4e7msxtlmO2lim1%2BFh8%2BIck%2FlPjr%2BRzmzQqUD7irWzs%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C2d00ea036378467d3da508d7f5ccd652%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248132431140642&sdata=4e7msxtlmO2lim1%2BFh8%2BIck%2FlPjr%2BRzmzQqUD7irWzs%3D&reserved=0
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C2d00ea036378467d3da508d7f5ccd652%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248132431140642&sdata=ddTEKth7I0HiTePSjA8KUEBLrhijnvdcdcEKz6YMq8Q%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C2d00ea036378467d3da508d7f5ccd652%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248132431140642&sdata=Q%2BCIVUtZmPqgd%2F0y5W7hUN5Q6Qf2IXXXmkrjSF8AKlI%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
Carlos Rovira
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C2d00ea036378467d3da508d7f5ccd652%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248132431140642&sdata=v1cL4dNh%2Bm3oRRRAa%2Fd5G2HgodjqcmBY8Oic3ZvlED8%3D&reserved=0
RE: Modules in IE
Posted by Yishay Weiss <yi...@hotmail.com>.
Carlos, I did replace all occurrences of inject_html with inject_script.
Piotr, I’ve removed support for inject_html to keep the compiler code simple, and because the same results can be achieved with inject_script without it unexpectedly messing up modules. After we’ve merged this I’ll send a heads-up on users and dev. In my opinion, since were not quite at 1.0, it’s ok to change the API like this if there’s a long term benefit.
From: Carlos Rovira<ma...@apache.org>
Sent: Friday, May 15, 2020 5:07 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: Modules in IE
Hi,
I suggest you try at least blog example 0012 (using external js),
jewel/royale-website and TDJ and update them accordingly to the new changes.
Searching in all royale-asjs for "inject_html" will give you the places and
examples where it's used, so you can check the actual uses and see how to
make it compatible with the actual state.
Thanks
El vie., 15 may. 2020 a las 16:01, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> Yishay,
>
> I just switched to your branches and inject_script is working properly with
> our application. However inject_html stopped working - is it expected
> behavior ?
>
> Thanks,
> Piotr
>
> czw., 14 maj 2020 o 19:33 Yishay Weiss <yi...@hotmail.com>
> napisał(a):
>
> > We can re-insert this feature if backwards compatibility becomes a big
> > enough issue. Looking forward, I agree with what you said before that we
> > should encourage less use of this pattern rather than more.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Thursday, May 14, 2020 6:52 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > FWIW, It occurred to me that we could leave inject_html in addition to
> > inject_script and just document that it doesn't work in modules and not
> use
> > it in the framework.
> >
> > Just a thought,
> > -Alex
> >
> > On 5/14/20, 8:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> >
> > Sure, will wait.
> >
> > Users will be required to change their inject_html annotations to
> > inject_script similar to what was done here [1]
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fcommit%2F14322f16c3ce44e7a4bdd2f3dc80f60e30842bd0&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=m97rrA1IIlrrTKyE9nDFO9SfCh5q3SAHrMwpd1%2BnV00%3D&reserved=0
> >
> > From: Piotr Zarzycki<ma...@gmail.com>
> > Sent: Thursday, May 14, 2020 5:56 PM
> > To: Apache Royale Development<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Please give me one more day more - Wait till Saturday. I would like
> to
> > test
> > your changes tomorrow with our application, so I would not run into
> > some
> > trouble with the next SDK update. As I understand the same name of
> the
> > branch applies also for compiler changes ?
> >
> > czw., 14 maj 2020 o 16:51 Yishay Weiss <yi...@hotmail.com>
> > napisał(a):
> >
> > > I’ve implemented this idea in inject_script branches for compiler
> and
> > > as-js. If someone has time test those it would be very helpful. It
> > works
> > > for my case. I’ll do some more basic testing and if there are no
> > objections
> > > I’ll merge tomorrow. Thanks.
> > >
> > > From: Alex Harui<ma...@adobe.com.INVALID>
> > > Sent: Monday, May 11, 2020 8:05 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > My idea wasn't quite that. It was to write the injection in JS
> > instead of
> > > HTML. Here's a current inject_html from dialogPolyfill.as
> > >
> > > /**
> > > * <inject_html>
> > > * <script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=NRqG0jKqi9%2B4rZSOXkolO7OIKtAkzgrVJXhdzR%2B5l7I%3D&reserved=0
> > > "></script<
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js%2522%253e%253c%2Fscript&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=2PlimX1AeQm4CV9LRsVZJnIxvP6zujyaOK09GLYSmrI%3D&reserved=0
> > > >>
> > > * <link rel="stylesheet" type="text/css" href="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=Q52Eb7XLAV1cYR4iloI%2BQXL64XD9gwQYEFDydjOb7cg%3D&reserved=0
> > > ">
> > > * </inject_html>
> > > */
> > >
> > > I think if it was rewritten as:
> > >
> > > /**
> > > * <inject_script>
> > > * var script = document.createElement("script");
> > > * script.setAttribute("src", "
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=NRqG0jKqi9%2B4rZSOXkolO7OIKtAkzgrVJXhdzR%2B5l7I%3D&reserved=0
> > > ");
> > > * document.head.appendChild(script)
> > > * var link = document.createElement("link");
> > > * link.setAttribute("rel", "stylesheet");
> > > * link.setAttribute("type", "text/css");
> > > * link.setAttribute("href", "
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=MhWWj%2BwxeRxK3%2B3xpq4UqY%2FDOaL6WiDbLnvdr%2BRRSio%3D&reserved=0
> > > ");
> > > * document.head.appendChild(link);
> > > * </inject_script>
> > > */
> > >
> > > Then all the compiler needs to do is copy that JS into the
> > appropriate
> > > file. I suppose we could always prepend it to the .js file, but I
> > think if
> > > we wanted we could inject it into the html wrapper by copying the
> > entire
> > > contents in between <script></script> tags.
> > >
> > > The compiler would not have to parse anything, just copy like it
> > currently
> > > does. We would have to go and re-write all of the current
> > inject_htmls,
> > > although, as I said earlier, I think many inject_htmls should be
> > replaced
> > > by other mechanism like static initializers. The real need for
> > > inject_html/inject_script is to make sure some external dependency
> > has been
> > > loaded so a class can initialize (as the various clss.prototype.foo
> > get
> > > interpreted). If the class just needs the dependency at runtime,
> > load it
> > > later in the code for the class. That makes it more PAYG as well.
> > >
> > > Of course, I could be wrong...
> > > -Alex
> > >
> > > On 5/11/20, 9:18 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> > >
> > > I guess I could add
> > >
> > > <inject_script src=””/> and <inject_link href=””/> syntax which
> > would
> > > be easier to parse and then transpile that, similar to how it’s
> done
> > today.
> > > Before I go too crazy though, can someone remind me why outerHTML
> is
> > evil?
> > >
> > > Thanks.
> > >
> > > From: Yishay Weiss<ma...@hotmail.com>
> > > Sent: Monday, May 11, 2020 7:00 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: RE: Modules in IE
> > >
> > >
> > > >What if we abandon "inject_html" and go with "inject_script"
> > > instead? Then when adding to the html output, each >script would
> be
> > > wrapped with a <script> tag, but for modules the code could be
> added
> > to the
> > > main module .js file.
> > > I’m not sure about this. I think typically you inject a <link
> > > href=”x”> for css and a <script src=”y”> for the js. How do you
> > propose to
> > > add those to the module js?
> > >
> > > On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com>
> > wrote:
> > >
> > > Hi Carlos, thanks. The issue is with inject_html in modules
> > on IE,
> > > dialogPolyfill.js just happened to be the target src here. I’ve
> been
> > > searching the net for solutions on IE and I think the trick is to
> > append
> > > elements instead of changing the inner html. I see two options of
> > > transpiling <inject_html> that would work on IE:
> > >
> > >
> > > 1. Parse the <inject_html> contents in the compiler and
> > create
> > > js that would work for IE. Difficult.
> > > 2. Replace each line in <inject_html> with dummy
> elements
> > and
> > > change their outerHTML to match each line contents. This one looks
> > easier,
> > > but I seem to remember a thread where we were trying to eliminate
> > use of
> > > outerHTML.
> > >
> > >
> > > Any thoughts are welcome.
> > >
> > > From: Carlos Rovira<ma...@apache.org>
> > > Sent: Monday, May 11, 2020 6:06 PM
> > > To: Apache Royale Development<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > Hi Yishay,
> > >
> > > talking without a huge analisys of the problem. I think
> Jewel
> > > Alert works
> > > ok in IE11 so that should mean dialogpolyfil is loading ok.
> > if not
> > > the case
> > > something broke recently since I checked that in TDJ and
> > other
> > > apps we did.
> > >
> > > Anyway, the commit you state is just to give the support we
> > > needed. I
> > > didn't tested in IE11, so don't know if we support it.
> > Normally
> > > IE11 use to
> > > require
> > > some special way of writing the code for some particular
> > things,
> > > so I think
> > > the way to solve this is:
> > >
> > > 1.- search in SOF or other sources how IE11 expect scripts
> > to be
> > > added
> > > dynamically
> > > 2.- upgrade the compiler code to use that way with that
> > > considerations to
> > > make it IE11 compatible and check if that works for IE11
> and
> > rest
> > > of
> > > browsers.
> > >
> > > sorry to not be able to say much more, but I'm these days
> > with few
> > > time
> > >
> > > Thanks
> > >
> > >
> > >
> > > El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<
> > > yishayjobs@hotmail.com>)
> > > escribió:
> > >
> > > > Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3
> in
> > > compiler code
> > > > doesn’t work for IE11. Any ideas on how to fix this?
> > > >
> > > > From: Yishay Weiss<ma...@hotmail.com>
> > > > Sent: Monday, May 11, 2020 4:52 PM
> > > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > > Subject: RE: Modules in IE
> > > >
> > > > These lines in dialogPolyfill.as
> > > >
> > > > * <inject_html>
> > > > * <script src="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > > > "></script>
> > > >
> > > > get transpiled to
> > > >
> > > > document.head.innerHTML += '<script src="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > > > "></script>'
> > > >
> > > > But that’s making IE11 fail in loading the module. It
> > doesn’t
> > > matter what
> > > > the src is, IE will silently fail. For example, I’m
> > getting the
> > > same result
> > > > if I replace the above with
> > > >
> > > > document.head.innerHTML += '<script></script>'
> > > >
> > > >
> > > >
> > > >
> > > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > > Sent: Sunday, May 10, 2020 7:35:55 PM
> > > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > Does dialog-polyfill load correctly? Does it muck with
> the
> > > window object?
> > > >
> > > > On 5/10/20, 9:13 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > > >
> > > > Test1.js isn’t different, but Test1_deps.js is.
> > > >
> > > > diff --git
> > "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > > index 73eccbe..3e1a8a7 100644
> > > > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > > +++
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > > @@ -211,4 +211,4 @@
> > > >
> > >
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > > > ['org
> > > > goog.addDependency('../../../XML.js', ['XML'], []);
> > > >
> > > > goog.require('Test1');
> > > > -document.head.innerHTML += '<script src="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > > > "></script<
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > > > >>';document.head.innerHTM
> > > > L += '<link rel="stylesheet" type="text/css" href="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=MhWWj%2BwxeRxK3%2B3xpq4UqY%2FDOaL6WiDbLnvdr%2BRRSio%3D&reserved=0
> > > > ">';
> > > > +
> > > >
> > > > From: Alex Harui<ma...@adobe.com.INVALID>
> > > > Sent: Sunday, May 10, 2020 6:39 PM
> > > > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > > > Subject: Re: Modules in IE
> > > >
> > > > Interesting. Just adding import shouldn't affect the
> > > output. What is
> > > > the difference between Test1.js with and without that
> > import
> > > statement?
> > > >
> > > > -Alex
> > > >
> > > > On 5/10/20, 8:31 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > > >
> > > > I’ve narrowed it down to usage of
> > mx.controls.Alert.
> > > Test case is
> > > > included in this issue [1].
> > > >
> > > > [1]
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=68mJrbzM53Hv%2BVOhisegFZAjSR%2BJktMnDOeUQoXKwqg%3D&reserved=0
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> >
> > > > Sent: Thursday, May 7, 2020 10:35 PM
> > > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > I think you can verify by debugging in some other
> > > browser and see
> > > > if breakpoints get set.
> > > >
> > > > A common “bug” in Flex modules was to reference
> > and link
> > > the
> > > > module class into the loading app. I have no idea what
> > will
> > > happen if you
> > > > have such a situation in Royale. You can look at the
> > loading
> > > app’s
> > > > link-report to see if the module (Test1) is linked in the
> > app
> > > and probably
> > > > see if Test1.js is in the output of the app if you start
> > clean
> > > and do not
> > > > compile the module.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > From: Yishay Weiss <yi...@hotmail.com>
> > > > Reply-To: "dev@royale.apache.org" <
> > dev@royale.apache.org
> > > >
> > > > Date: Thursday, May 7, 2020 at 12:26 PM
> > > > To: "dev@royale.apache.org" <
> dev@royale.apache.org
> > >
> > > > Subject: RE: Modules in IE
> > > >
> > > > url is
> > > >
> > > >
> > >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/><file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/><file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/%3e1.js%3cfile:/C:/dev/RoyaleCom>>>>>>>
> > > >
> > > > I don’t see errors other than
> > > >
> > > > SEC7113: CSS was ignored due to mime type
> mismatch
> > > >
> > > > But I don’t think that’s it.
> > > >
> > > > I put a debugger; statement on the first line of
> > the src
> > > which
> > > > never kicks.
> > > >
> > > >
> > > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > > > To: dev@royale.apache.org <dev@royale.apache.org
> >
> > > > Subject: Re: Modules in IE
> > > >
> > > > What is the src (url) for that script? Were
> there
> > any
> > > errors
> > > > loading and running it? Are the other Royale
> > packages/classes
> > > in the
> > > > "window" object?
> > > >
> > > > One scenario I thought of is that some bug or
> > something
> > > else
> > > > creates a "window" property at the global window causing
> > our
> > > package lookup
> > > > to be off.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com> wrote:
> > > >
> > > > In my example <script> element is there but
> > it’s
> > > never loaded
> > > > on IE. I can confirm ModuleExamle works.
> > > >
> > > > From: Alex Harui<mailto:
> > aharui@adobe.com.INVALID>
> > > > Sent: Sunday, May 3, 2020 9:31 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > I just ran examples/royale/ModuleExample in
> IE
> > and
> > > it worked.
> > > > Does it work for you?
> > > > In the debugger, window.Module and
> > window.MainApp
> > > resolve to
> > > > functions. window.org is an object with an apache
> > property.
> > > > In the DOM Explorer, there should be tons of
> > > <script> tags in
> > > > the head. Near the end of the list should be the script
> > for the
> > > .js file
> > > > for the module.
> > > > Do you see any exceptions? ModuleExample
> works
> > > without errors.
> > > >
> > > > -Alex
> > > >
> > > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com>
> > > > wrote:
> > > >
> > > > 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:
> > aharui@adobe.com.INVALID
> > > >
> > > > Sent: Thursday, April 30, 2020 6:29 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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:
> > > aharui@adobe.com.INVALID>
> > > > Sent: Thursday, April 30, 2020 12:00
> AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org
> > > > >
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> >
> > > > Sent: Wednesday, May 6, 2020 7:58 PM
> > > > Subject: Re: Modules in IE
> > > >
> > > > What is the src (url) for that script? Were
> there
> > any
> > > errors
> > > > loading and running it? Are the other Royale
> > packages/classes
> > > in the
> > > > "window" object?
> > > >
> > > > One scenario I thought of is that some bug or
> > something
> > > else
> > > > creates a "window" property at the global window causing
> > our
> > > package lookup
> > > > to be off.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com> wrote:
> > > >
> > > > In my example <script> element is there but
> > it’s
> > > never loaded
> > > > on IE. I can confirm ModuleExamle works.
> > > >
> > > > From: Alex Harui<mailto:
> > aharui@adobe.com.INVALID>
> > > > Sent: Sunday, May 3, 2020 9:31 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > I just ran examples/royale/ModuleExample in
> IE
> > and
> > > it worked.
> > > > Does it work for you?
> > > > In the debugger, window.Module and
> > window.MainApp
> > > resolve to
> > > > functions. window.org is an object with an apache
> > property.
> > > > In the DOM Explorer, there should be tons of
> > > <script> tags in
> > > > the head. Near the end of the list should be the script
> > for the
> > > .js file
> > > > for the module.
> > > > Do you see any exceptions? ModuleExample
> works
> > > without errors.
> > > >
> > > > -Alex
> > > >
> > > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com>
> > > > wrote:
> > > >
> > > > 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:
> > aharui@adobe.com.INVALID
> > > >
> > > > Sent: Thursday, April 30, 2020 6:29 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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:
> > > aharui@adobe.com.INVALID>
> > > > Sent: Thursday, April 30, 2020 12:00
> AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org
> > > > >
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > From: Alex Harui<ma...@adobe.com.INVALID>
> > > > Sent: Sunday, May 10, 2020 7:36 PM
> > > > Subject: Re: Modules in IE
> > > >
> > > > Does dialog-polyfill load correctly? Does it muck with
> the
> > > window object?
> > > >
> > > > On 5/10/20, 9:13 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > > >
> > > > Test1.js isn’t different, but Test1_deps.js is.
> > > >
> > > > diff --git
> > "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > > index 73eccbe..3e1a8a7 100644
> > > > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > > +++
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > > @@ -211,4 +211,4 @@
> > > >
> > >
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > > > ['org
> > > > goog.addDependency('../../../XML.js', ['XML'], []);
> > > >
> > > > goog.require('Test1');
> > > > -document.head.innerHTML += '<script src="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > > > "></script<
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > > > >>';document.head.innerHTM
> > > > L += '<link rel="stylesheet" type="text/css" href="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=MhWWj%2BwxeRxK3%2B3xpq4UqY%2FDOaL6WiDbLnvdr%2BRRSio%3D&reserved=0
> > > > ">';
> > > > +
> > > >
> > > > From: Alex Harui<ma...@adobe.com.INVALID>
> > > > Sent: Sunday, May 10, 2020 6:39 PM
> > > > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > > > Subject: Re: Modules in IE
> > > >
> > > > Interesting. Just adding import shouldn't affect the
> > > output. What is
> > > > the difference between Test1.js with and without that
> > import
> > > statement?
> > > >
> > > > -Alex
> > > >
> > > > On 5/10/20, 8:31 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > > >
> > > > I’ve narrowed it down to usage of
> > mx.controls.Alert.
> > > Test case is
> > > > included in this issue [1].
> > > >
> > > > [1]
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=68mJrbzM53Hv%2BVOhisegFZAjSR%2BJktMnDOeUQoXKwqg%3D&reserved=0
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> >
> > > > Sent: Thursday, May 7, 2020 10:35 PM
> > > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > I think you can verify by debugging in some other
> > > browser and see
> > > > if breakpoints get set.
> > > >
> > > > A common “bug” in Flex modules was to reference
> > and link
> > > the
> > > > module class into the loading app. I have no idea what
> > will
> > > happen if you
> > > > have such a situation in Royale. You can look at the
> > loading
> > > app’s
> > > > link-report to see if the module (Test1) is linked in the
> > app
> > > and probably
> > > > see if Test1.js is in the output of the app if you start
> > clean
> > > and do not
> > > > compile the module.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > From: Yishay Weiss <yi...@hotmail.com>
> > > > Reply-To: "dev@royale.apache.org" <
> > dev@royale.apache.org
> > > >
> > > > Date: Thursday, May 7, 2020 at 12:26 PM
> > > > To: "dev@royale.apache.org" <
> dev@royale.apache.org
> > >
> > > > Subject: RE: Modules in IE
> > > >
> > > > url is
> > > >
> > > >
> > >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentT<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/Royal<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/><file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>eComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/%3eeComponentTest/NewComponentTe>>est/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>>>>>>
> > > >
> > > > I don’t see errors other than
> > > >
> > > > SEC7113: CSS was ignored due to mime type
> mismatch
> > > >
> > > > But I don’t think that’s it.
> > > >
> > > > I put a debugger; statement on the first line of
> > the src
> > > which
> > > > never kicks.
> > > >
> > > >
> > > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > > > To: dev@royale.apache.org <dev@royale.apache.org
> >
> > > > Subject: Re: Modules in IE
> > > >
> > > > What is the src (url) for that script? Were
> there
> > any
> > > errors
> > > > loading and running it? Are the other Royale
> > packages/classes
> > > in the
> > > > "window" object?
> > > >
> > > > One scenario I thought of is that some bug or
> > something
> > > else
> > > > creates a "window" property at the global window causing
> > our
> > > package lookup
> > > > to be off.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com> wrote:
> > > >
> > > > In my example <script> element is there but
> > it’s
> > > never loaded
> > > > on IE. I can confirm ModuleExamle works.
> > > >
> > > > From: Alex Harui<mailto:
> > aharui@adobe.com.INVALID>
> > > > Sent: Sunday, May 3, 2020 9:31 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > I just ran examples/royale/ModuleExample in
> IE
> > and
> > > it worked.
> > > > Does it work for you?
> > > > In the debugger, window.Module and
> > window.MainApp
> > > resolve to
> > > > functions. window.org is an object with an apache
> > property.
> > > > In the DOM Explorer, there should be tons of
> > > <script> tags in
> > > > the head. Near the end of the list should be the script
> > for the
> > > .js file
> > > > for the module.
> > > > Do you see any exceptions? ModuleExample
> works
> > > without errors.
> > > >
> > > > -Alex
> > > >
> > > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com>
> > > > wrote:
> > > >
> > > > 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:
> > aharui@adobe.com.INVALID
> > > >
> > > > Sent: Thursday, April 30, 2020 6:29 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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:
> > > aharui@adobe.com.INVALID>
> > > > Sent: Thursday, April 30, 2020 12:00
> AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org
> > > > >
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> >
> > > > Sent: Wednesday, May 6, 2020 7:58 PM
> > > > Subject: Re: Modules in IE
> > > >
> > > > What is the src (url) for that script? Were
> there
> > any
> > > errors
> > > > loading and running it? Are the other Royale
> > packages/classes
> > > in the
> > > > "window" object?
> > > >
> > > > One scenario I thought of is that some bug or
> > something
> > > else
> > > > creates a "window" property at the global window causing
> > our
> > > package lookup
> > > > to be off.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com> wrote:
> > > >
> > > > In my example <script> element is there but
> > it’s
> > > never loaded
> > > > on IE. I can confirm ModuleExamle works.
> > > >
> > > > From: Alex Harui<mailto:
> > aharui@adobe.com.INVALID>
> > > > Sent: Sunday, May 3, 2020 9:31 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > I just ran examples/royale/ModuleExample in
> IE
> > and
> > > it worked.
> > > > Does it work for you?
> > > > In the debugger, window.Module and
> > window.MainApp
> > > resolve to
> > > > functions. window.org is an object with an apache
> > property.
> > > > In the DOM Explorer, there should be tons of
> > > <script> tags in
> > > > the head. Near the end of the list should be the script
> > for the
> > > .js file
> > > > for the module.
> > > > Do you see any exceptions? ModuleExample
> works
> > > without errors.
> > > >
> > > > -Alex
> > > >
> > > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com>
> > > > wrote:
> > > >
> > > > 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:
> > aharui@adobe.com.INVALID
> > > >
> > > > Sent: Thursday, April 30, 2020 6:29 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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:
> > > aharui@adobe.com.INVALID>
> > > > Sent: Thursday, April 30, 2020 12:00
> AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org
> > > > >
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > > --
> > > Carlos Rovira
> > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uQa7YC%2BnUiA99EK2Bp7Zt4XoGM83QGHud18jHOuiozQ%3D&reserved=0
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862253347&sdata=ut8lSfyDfOHTSPTY3R5j3LYFwOGV%2BTA9NurMwtvpxks%3D&reserved=0
> > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862253347&sdata=ut8lSfyDfOHTSPTY3R5j3LYFwOGV%2BTA9NurMwtvpxks%3D&reserved=0
> > >*
> >
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Modules in IE
Posted by Carlos Rovira <ca...@apache.org>.
Hi,
I suggest you try at least blog example 0012 (using external js),
jewel/royale-website and TDJ and update them accordingly to the new changes.
Searching in all royale-asjs for "inject_html" will give you the places and
examples where it's used, so you can check the actual uses and see how to
make it compatible with the actual state.
Thanks
El vie., 15 may. 2020 a las 16:01, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> Yishay,
>
> I just switched to your branches and inject_script is working properly with
> our application. However inject_html stopped working - is it expected
> behavior ?
>
> Thanks,
> Piotr
>
> czw., 14 maj 2020 o 19:33 Yishay Weiss <yi...@hotmail.com>
> napisał(a):
>
> > We can re-insert this feature if backwards compatibility becomes a big
> > enough issue. Looking forward, I agree with what you said before that we
> > should encourage less use of this pattern rather than more.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Thursday, May 14, 2020 6:52 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > FWIW, It occurred to me that we could leave inject_html in addition to
> > inject_script and just document that it doesn't work in modules and not
> use
> > it in the framework.
> >
> > Just a thought,
> > -Alex
> >
> > On 5/14/20, 8:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> >
> > Sure, will wait.
> >
> > Users will be required to change their inject_html annotations to
> > inject_script similar to what was done here [1]
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fcommit%2F14322f16c3ce44e7a4bdd2f3dc80f60e30842bd0&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=m97rrA1IIlrrTKyE9nDFO9SfCh5q3SAHrMwpd1%2BnV00%3D&reserved=0
> >
> > From: Piotr Zarzycki<ma...@gmail.com>
> > Sent: Thursday, May 14, 2020 5:56 PM
> > To: Apache Royale Development<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Please give me one more day more - Wait till Saturday. I would like
> to
> > test
> > your changes tomorrow with our application, so I would not run into
> > some
> > trouble with the next SDK update. As I understand the same name of
> the
> > branch applies also for compiler changes ?
> >
> > czw., 14 maj 2020 o 16:51 Yishay Weiss <yi...@hotmail.com>
> > napisał(a):
> >
> > > I’ve implemented this idea in inject_script branches for compiler
> and
> > > as-js. If someone has time test those it would be very helpful. It
> > works
> > > for my case. I’ll do some more basic testing and if there are no
> > objections
> > > I’ll merge tomorrow. Thanks.
> > >
> > > From: Alex Harui<ma...@adobe.com.INVALID>
> > > Sent: Monday, May 11, 2020 8:05 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > My idea wasn't quite that. It was to write the injection in JS
> > instead of
> > > HTML. Here's a current inject_html from dialogPolyfill.as
> > >
> > > /**
> > > * <inject_html>
> > > * <script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=NRqG0jKqi9%2B4rZSOXkolO7OIKtAkzgrVJXhdzR%2B5l7I%3D&reserved=0
> > > "></script<
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js%2522%253e%253c%2Fscript&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=2PlimX1AeQm4CV9LRsVZJnIxvP6zujyaOK09GLYSmrI%3D&reserved=0
> > > >>
> > > * <link rel="stylesheet" type="text/css" href="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=Q52Eb7XLAV1cYR4iloI%2BQXL64XD9gwQYEFDydjOb7cg%3D&reserved=0
> > > ">
> > > * </inject_html>
> > > */
> > >
> > > I think if it was rewritten as:
> > >
> > > /**
> > > * <inject_script>
> > > * var script = document.createElement("script");
> > > * script.setAttribute("src", "
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=NRqG0jKqi9%2B4rZSOXkolO7OIKtAkzgrVJXhdzR%2B5l7I%3D&reserved=0
> > > ");
> > > * document.head.appendChild(script)
> > > * var link = document.createElement("link");
> > > * link.setAttribute("rel", "stylesheet");
> > > * link.setAttribute("type", "text/css");
> > > * link.setAttribute("href", "
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=MhWWj%2BwxeRxK3%2B3xpq4UqY%2FDOaL6WiDbLnvdr%2BRRSio%3D&reserved=0
> > > ");
> > > * document.head.appendChild(link);
> > > * </inject_script>
> > > */
> > >
> > > Then all the compiler needs to do is copy that JS into the
> > appropriate
> > > file. I suppose we could always prepend it to the .js file, but I
> > think if
> > > we wanted we could inject it into the html wrapper by copying the
> > entire
> > > contents in between <script></script> tags.
> > >
> > > The compiler would not have to parse anything, just copy like it
> > currently
> > > does. We would have to go and re-write all of the current
> > inject_htmls,
> > > although, as I said earlier, I think many inject_htmls should be
> > replaced
> > > by other mechanism like static initializers. The real need for
> > > inject_html/inject_script is to make sure some external dependency
> > has been
> > > loaded so a class can initialize (as the various clss.prototype.foo
> > get
> > > interpreted). If the class just needs the dependency at runtime,
> > load it
> > > later in the code for the class. That makes it more PAYG as well.
> > >
> > > Of course, I could be wrong...
> > > -Alex
> > >
> > > On 5/11/20, 9:18 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> > >
> > > I guess I could add
> > >
> > > <inject_script src=””/> and <inject_link href=””/> syntax which
> > would
> > > be easier to parse and then transpile that, similar to how it’s
> done
> > today.
> > > Before I go too crazy though, can someone remind me why outerHTML
> is
> > evil?
> > >
> > > Thanks.
> > >
> > > From: Yishay Weiss<ma...@hotmail.com>
> > > Sent: Monday, May 11, 2020 7:00 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: RE: Modules in IE
> > >
> > >
> > > >What if we abandon "inject_html" and go with "inject_script"
> > > instead? Then when adding to the html output, each >script would
> be
> > > wrapped with a <script> tag, but for modules the code could be
> added
> > to the
> > > main module .js file.
> > > I’m not sure about this. I think typically you inject a <link
> > > href=”x”> for css and a <script src=”y”> for the js. How do you
> > propose to
> > > add those to the module js?
> > >
> > > On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com>
> > wrote:
> > >
> > > Hi Carlos, thanks. The issue is with inject_html in modules
> > on IE,
> > > dialogPolyfill.js just happened to be the target src here. I’ve
> been
> > > searching the net for solutions on IE and I think the trick is to
> > append
> > > elements instead of changing the inner html. I see two options of
> > > transpiling <inject_html> that would work on IE:
> > >
> > >
> > > 1. Parse the <inject_html> contents in the compiler and
> > create
> > > js that would work for IE. Difficult.
> > > 2. Replace each line in <inject_html> with dummy
> elements
> > and
> > > change their outerHTML to match each line contents. This one looks
> > easier,
> > > but I seem to remember a thread where we were trying to eliminate
> > use of
> > > outerHTML.
> > >
> > >
> > > Any thoughts are welcome.
> > >
> > > From: Carlos Rovira<ma...@apache.org>
> > > Sent: Monday, May 11, 2020 6:06 PM
> > > To: Apache Royale Development<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > Hi Yishay,
> > >
> > > talking without a huge analisys of the problem. I think
> Jewel
> > > Alert works
> > > ok in IE11 so that should mean dialogpolyfil is loading ok.
> > if not
> > > the case
> > > something broke recently since I checked that in TDJ and
> > other
> > > apps we did.
> > >
> > > Anyway, the commit you state is just to give the support we
> > > needed. I
> > > didn't tested in IE11, so don't know if we support it.
> > Normally
> > > IE11 use to
> > > require
> > > some special way of writing the code for some particular
> > things,
> > > so I think
> > > the way to solve this is:
> > >
> > > 1.- search in SOF or other sources how IE11 expect scripts
> > to be
> > > added
> > > dynamically
> > > 2.- upgrade the compiler code to use that way with that
> > > considerations to
> > > make it IE11 compatible and check if that works for IE11
> and
> > rest
> > > of
> > > browsers.
> > >
> > > sorry to not be able to say much more, but I'm these days
> > with few
> > > time
> > >
> > > Thanks
> > >
> > >
> > >
> > > El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<
> > > yishayjobs@hotmail.com>)
> > > escribió:
> > >
> > > > Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3
> in
> > > compiler code
> > > > doesn’t work for IE11. Any ideas on how to fix this?
> > > >
> > > > From: Yishay Weiss<ma...@hotmail.com>
> > > > Sent: Monday, May 11, 2020 4:52 PM
> > > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > > Subject: RE: Modules in IE
> > > >
> > > > These lines in dialogPolyfill.as
> > > >
> > > > * <inject_html>
> > > > * <script src="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > > > "></script>
> > > >
> > > > get transpiled to
> > > >
> > > > document.head.innerHTML += '<script src="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > > > "></script>'
> > > >
> > > > But that’s making IE11 fail in loading the module. It
> > doesn’t
> > > matter what
> > > > the src is, IE will silently fail. For example, I’m
> > getting the
> > > same result
> > > > if I replace the above with
> > > >
> > > > document.head.innerHTML += '<script></script>'
> > > >
> > > >
> > > >
> > > >
> > > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > > Sent: Sunday, May 10, 2020 7:35:55 PM
> > > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > Does dialog-polyfill load correctly? Does it muck with
> the
> > > window object?
> > > >
> > > > On 5/10/20, 9:13 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > > >
> > > > Test1.js isn’t different, but Test1_deps.js is.
> > > >
> > > > diff --git
> > "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > > index 73eccbe..3e1a8a7 100644
> > > > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > > +++
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > > @@ -211,4 +211,4 @@
> > > >
> > >
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > > > ['org
> > > > goog.addDependency('../../../XML.js', ['XML'], []);
> > > >
> > > > goog.require('Test1');
> > > > -document.head.innerHTML += '<script src="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > > > "></script<
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > > > >>';document.head.innerHTM
> > > > L += '<link rel="stylesheet" type="text/css" href="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=MhWWj%2BwxeRxK3%2B3xpq4UqY%2FDOaL6WiDbLnvdr%2BRRSio%3D&reserved=0
> > > > ">';
> > > > +
> > > >
> > > > From: Alex Harui<ma...@adobe.com.INVALID>
> > > > Sent: Sunday, May 10, 2020 6:39 PM
> > > > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > > > Subject: Re: Modules in IE
> > > >
> > > > Interesting. Just adding import shouldn't affect the
> > > output. What is
> > > > the difference between Test1.js with and without that
> > import
> > > statement?
> > > >
> > > > -Alex
> > > >
> > > > On 5/10/20, 8:31 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > > >
> > > > I’ve narrowed it down to usage of
> > mx.controls.Alert.
> > > Test case is
> > > > included in this issue [1].
> > > >
> > > > [1]
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=68mJrbzM53Hv%2BVOhisegFZAjSR%2BJktMnDOeUQoXKwqg%3D&reserved=0
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> >
> > > > Sent: Thursday, May 7, 2020 10:35 PM
> > > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > I think you can verify by debugging in some other
> > > browser and see
> > > > if breakpoints get set.
> > > >
> > > > A common “bug” in Flex modules was to reference
> > and link
> > > the
> > > > module class into the loading app. I have no idea what
> > will
> > > happen if you
> > > > have such a situation in Royale. You can look at the
> > loading
> > > app’s
> > > > link-report to see if the module (Test1) is linked in the
> > app
> > > and probably
> > > > see if Test1.js is in the output of the app if you start
> > clean
> > > and do not
> > > > compile the module.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > From: Yishay Weiss <yi...@hotmail.com>
> > > > Reply-To: "dev@royale.apache.org" <
> > dev@royale.apache.org
> > > >
> > > > Date: Thursday, May 7, 2020 at 12:26 PM
> > > > To: "dev@royale.apache.org" <
> dev@royale.apache.org
> > >
> > > > Subject: RE: Modules in IE
> > > >
> > > > url is
> > > >
> > > >
> > >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/><file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/%3e1.js%3cfile:/C:/dev/RoyaleCom>>>>>>>
> > > >
> > > > I don’t see errors other than
> > > >
> > > > SEC7113: CSS was ignored due to mime type
> mismatch
> > > >
> > > > But I don’t think that’s it.
> > > >
> > > > I put a debugger; statement on the first line of
> > the src
> > > which
> > > > never kicks.
> > > >
> > > >
> > > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > > > To: dev@royale.apache.org <dev@royale.apache.org
> >
> > > > Subject: Re: Modules in IE
> > > >
> > > > What is the src (url) for that script? Were
> there
> > any
> > > errors
> > > > loading and running it? Are the other Royale
> > packages/classes
> > > in the
> > > > "window" object?
> > > >
> > > > One scenario I thought of is that some bug or
> > something
> > > else
> > > > creates a "window" property at the global window causing
> > our
> > > package lookup
> > > > to be off.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com> wrote:
> > > >
> > > > In my example <script> element is there but
> > it’s
> > > never loaded
> > > > on IE. I can confirm ModuleExamle works.
> > > >
> > > > From: Alex Harui<mailto:
> > aharui@adobe.com.INVALID>
> > > > Sent: Sunday, May 3, 2020 9:31 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > I just ran examples/royale/ModuleExample in
> IE
> > and
> > > it worked.
> > > > Does it work for you?
> > > > In the debugger, window.Module and
> > window.MainApp
> > > resolve to
> > > > functions. window.org is an object with an apache
> > property.
> > > > In the DOM Explorer, there should be tons of
> > > <script> tags in
> > > > the head. Near the end of the list should be the script
> > for the
> > > .js file
> > > > for the module.
> > > > Do you see any exceptions? ModuleExample
> works
> > > without errors.
> > > >
> > > > -Alex
> > > >
> > > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com>
> > > > wrote:
> > > >
> > > > 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:
> > aharui@adobe.com.INVALID
> > > >
> > > > Sent: Thursday, April 30, 2020 6:29 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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:
> > > aharui@adobe.com.INVALID>
> > > > Sent: Thursday, April 30, 2020 12:00
> AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org
> > > > >
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> >
> > > > Sent: Wednesday, May 6, 2020 7:58 PM
> > > > Subject: Re: Modules in IE
> > > >
> > > > What is the src (url) for that script? Were
> there
> > any
> > > errors
> > > > loading and running it? Are the other Royale
> > packages/classes
> > > in the
> > > > "window" object?
> > > >
> > > > One scenario I thought of is that some bug or
> > something
> > > else
> > > > creates a "window" property at the global window causing
> > our
> > > package lookup
> > > > to be off.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com> wrote:
> > > >
> > > > In my example <script> element is there but
> > it’s
> > > never loaded
> > > > on IE. I can confirm ModuleExamle works.
> > > >
> > > > From: Alex Harui<mailto:
> > aharui@adobe.com.INVALID>
> > > > Sent: Sunday, May 3, 2020 9:31 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > I just ran examples/royale/ModuleExample in
> IE
> > and
> > > it worked.
> > > > Does it work for you?
> > > > In the debugger, window.Module and
> > window.MainApp
> > > resolve to
> > > > functions. window.org is an object with an apache
> > property.
> > > > In the DOM Explorer, there should be tons of
> > > <script> tags in
> > > > the head. Near the end of the list should be the script
> > for the
> > > .js file
> > > > for the module.
> > > > Do you see any exceptions? ModuleExample
> works
> > > without errors.
> > > >
> > > > -Alex
> > > >
> > > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com>
> > > > wrote:
> > > >
> > > > 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:
> > aharui@adobe.com.INVALID
> > > >
> > > > Sent: Thursday, April 30, 2020 6:29 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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:
> > > aharui@adobe.com.INVALID>
> > > > Sent: Thursday, April 30, 2020 12:00
> AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org
> > > > >
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > From: Alex Harui<ma...@adobe.com.INVALID>
> > > > Sent: Sunday, May 10, 2020 7:36 PM
> > > > Subject: Re: Modules in IE
> > > >
> > > > Does dialog-polyfill load correctly? Does it muck with
> the
> > > window object?
> > > >
> > > > On 5/10/20, 9:13 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > > >
> > > > Test1.js isn’t different, but Test1_deps.js is.
> > > >
> > > > diff --git
> > "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > > index 73eccbe..3e1a8a7 100644
> > > > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > > +++
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > > @@ -211,4 +211,4 @@
> > > >
> > >
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > > > ['org
> > > > goog.addDependency('../../../XML.js', ['XML'], []);
> > > >
> > > > goog.require('Test1');
> > > > -document.head.innerHTML += '<script src="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > > > "></script<
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > > > >>';document.head.innerHTM
> > > > L += '<link rel="stylesheet" type="text/css" href="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=MhWWj%2BwxeRxK3%2B3xpq4UqY%2FDOaL6WiDbLnvdr%2BRRSio%3D&reserved=0
> > > > ">';
> > > > +
> > > >
> > > > From: Alex Harui<ma...@adobe.com.INVALID>
> > > > Sent: Sunday, May 10, 2020 6:39 PM
> > > > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > > > Subject: Re: Modules in IE
> > > >
> > > > Interesting. Just adding import shouldn't affect the
> > > output. What is
> > > > the difference between Test1.js with and without that
> > import
> > > statement?
> > > >
> > > > -Alex
> > > >
> > > > On 5/10/20, 8:31 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > > >
> > > > I’ve narrowed it down to usage of
> > mx.controls.Alert.
> > > Test case is
> > > > included in this issue [1].
> > > >
> > > > [1]
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=68mJrbzM53Hv%2BVOhisegFZAjSR%2BJktMnDOeUQoXKwqg%3D&reserved=0
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> >
> > > > Sent: Thursday, May 7, 2020 10:35 PM
> > > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > I think you can verify by debugging in some other
> > > browser and see
> > > > if breakpoints get set.
> > > >
> > > > A common “bug” in Flex modules was to reference
> > and link
> > > the
> > > > module class into the loading app. I have no idea what
> > will
> > > happen if you
> > > > have such a situation in Royale. You can look at the
> > loading
> > > app’s
> > > > link-report to see if the module (Test1) is linked in the
> > app
> > > and probably
> > > > see if Test1.js is in the output of the app if you start
> > clean
> > > and do not
> > > > compile the module.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > From: Yishay Weiss <yi...@hotmail.com>
> > > > Reply-To: "dev@royale.apache.org" <
> > dev@royale.apache.org
> > > >
> > > > Date: Thursday, May 7, 2020 at 12:26 PM
> > > > To: "dev@royale.apache.org" <
> dev@royale.apache.org
> > >
> > > > Subject: RE: Modules in IE
> > > >
> > > > url is
> > > >
> > > >
> > >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentT<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/Royal<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>eComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>est/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>>>>>>
> > > >
> > > > I don’t see errors other than
> > > >
> > > > SEC7113: CSS was ignored due to mime type
> mismatch
> > > >
> > > > But I don’t think that’s it.
> > > >
> > > > I put a debugger; statement on the first line of
> > the src
> > > which
> > > > never kicks.
> > > >
> > > >
> > > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > > > To: dev@royale.apache.org <dev@royale.apache.org
> >
> > > > Subject: Re: Modules in IE
> > > >
> > > > What is the src (url) for that script? Were
> there
> > any
> > > errors
> > > > loading and running it? Are the other Royale
> > packages/classes
> > > in the
> > > > "window" object?
> > > >
> > > > One scenario I thought of is that some bug or
> > something
> > > else
> > > > creates a "window" property at the global window causing
> > our
> > > package lookup
> > > > to be off.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com> wrote:
> > > >
> > > > In my example <script> element is there but
> > it’s
> > > never loaded
> > > > on IE. I can confirm ModuleExamle works.
> > > >
> > > > From: Alex Harui<mailto:
> > aharui@adobe.com.INVALID>
> > > > Sent: Sunday, May 3, 2020 9:31 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > I just ran examples/royale/ModuleExample in
> IE
> > and
> > > it worked.
> > > > Does it work for you?
> > > > In the debugger, window.Module and
> > window.MainApp
> > > resolve to
> > > > functions. window.org is an object with an apache
> > property.
> > > > In the DOM Explorer, there should be tons of
> > > <script> tags in
> > > > the head. Near the end of the list should be the script
> > for the
> > > .js file
> > > > for the module.
> > > > Do you see any exceptions? ModuleExample
> works
> > > without errors.
> > > >
> > > > -Alex
> > > >
> > > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com>
> > > > wrote:
> > > >
> > > > 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:
> > aharui@adobe.com.INVALID
> > > >
> > > > Sent: Thursday, April 30, 2020 6:29 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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:
> > > aharui@adobe.com.INVALID>
> > > > Sent: Thursday, April 30, 2020 12:00
> AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org
> > > > >
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> >
> > > > Sent: Wednesday, May 6, 2020 7:58 PM
> > > > Subject: Re: Modules in IE
> > > >
> > > > What is the src (url) for that script? Were
> there
> > any
> > > errors
> > > > loading and running it? Are the other Royale
> > packages/classes
> > > in the
> > > > "window" object?
> > > >
> > > > One scenario I thought of is that some bug or
> > something
> > > else
> > > > creates a "window" property at the global window causing
> > our
> > > package lookup
> > > > to be off.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com> wrote:
> > > >
> > > > In my example <script> element is there but
> > it’s
> > > never loaded
> > > > on IE. I can confirm ModuleExamle works.
> > > >
> > > > From: Alex Harui<mailto:
> > aharui@adobe.com.INVALID>
> > > > Sent: Sunday, May 3, 2020 9:31 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > I just ran examples/royale/ModuleExample in
> IE
> > and
> > > it worked.
> > > > Does it work for you?
> > > > In the debugger, window.Module and
> > window.MainApp
> > > resolve to
> > > > functions. window.org is an object with an apache
> > property.
> > > > In the DOM Explorer, there should be tons of
> > > <script> tags in
> > > > the head. Near the end of the list should be the script
> > for the
> > > .js file
> > > > for the module.
> > > > Do you see any exceptions? ModuleExample
> works
> > > without errors.
> > > >
> > > > -Alex
> > > >
> > > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com>
> > > > wrote:
> > > >
> > > > 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:
> > aharui@adobe.com.INVALID
> > > >
> > > > Sent: Thursday, April 30, 2020 6:29 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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:
> > > aharui@adobe.com.INVALID>
> > > > Sent: Thursday, April 30, 2020 12:00
> AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org
> > > > >
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > > --
> > > Carlos Rovira
> > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uQa7YC%2BnUiA99EK2Bp7Zt4XoGM83QGHud18jHOuiozQ%3D&reserved=0
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862253347&sdata=ut8lSfyDfOHTSPTY3R5j3LYFwOGV%2BTA9NurMwtvpxks%3D&reserved=0
> > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862253347&sdata=ut8lSfyDfOHTSPTY3R5j3LYFwOGV%2BTA9NurMwtvpxks%3D&reserved=0
> > >*
> >
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Modules in IE
Posted by Piotr Zarzycki <pi...@gmail.com>.
Yishay,
I just switched to your branches and inject_script is working properly with
our application. However inject_html stopped working - is it expected
behavior ?
Thanks,
Piotr
czw., 14 maj 2020 o 19:33 Yishay Weiss <yi...@hotmail.com> napisał(a):
> We can re-insert this feature if backwards compatibility becomes a big
> enough issue. Looking forward, I agree with what you said before that we
> should encourage less use of this pattern rather than more.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 14, 2020 6:52 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> FWIW, It occurred to me that we could leave inject_html in addition to
> inject_script and just document that it doesn't work in modules and not use
> it in the framework.
>
> Just a thought,
> -Alex
>
> On 5/14/20, 8:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Sure, will wait.
>
> Users will be required to change their inject_html annotations to
> inject_script similar to what was done here [1]
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fcommit%2F14322f16c3ce44e7a4bdd2f3dc80f60e30842bd0&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=m97rrA1IIlrrTKyE9nDFO9SfCh5q3SAHrMwpd1%2BnV00%3D&reserved=0
>
> From: Piotr Zarzycki<ma...@gmail.com>
> Sent: Thursday, May 14, 2020 5:56 PM
> To: Apache Royale Development<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Please give me one more day more - Wait till Saturday. I would like to
> test
> your changes tomorrow with our application, so I would not run into
> some
> trouble with the next SDK update. As I understand the same name of the
> branch applies also for compiler changes ?
>
> czw., 14 maj 2020 o 16:51 Yishay Weiss <yi...@hotmail.com>
> napisał(a):
>
> > I’ve implemented this idea in inject_script branches for compiler and
> > as-js. If someone has time test those it would be very helpful. It
> works
> > for my case. I’ll do some more basic testing and if there are no
> objections
> > I’ll merge tomorrow. Thanks.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Monday, May 11, 2020 8:05 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > My idea wasn't quite that. It was to write the injection in JS
> instead of
> > HTML. Here's a current inject_html from dialogPolyfill.as
> >
> > /**
> > * <inject_html>
> > * <script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=NRqG0jKqi9%2B4rZSOXkolO7OIKtAkzgrVJXhdzR%2B5l7I%3D&reserved=0
> > "></script<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js%2522%253e%253c%2Fscript&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=2PlimX1AeQm4CV9LRsVZJnIxvP6zujyaOK09GLYSmrI%3D&reserved=0
> > >>
> > * <link rel="stylesheet" type="text/css" href="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=Q52Eb7XLAV1cYR4iloI%2BQXL64XD9gwQYEFDydjOb7cg%3D&reserved=0
> > ">
> > * </inject_html>
> > */
> >
> > I think if it was rewritten as:
> >
> > /**
> > * <inject_script>
> > * var script = document.createElement("script");
> > * script.setAttribute("src", "
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=NRqG0jKqi9%2B4rZSOXkolO7OIKtAkzgrVJXhdzR%2B5l7I%3D&reserved=0
> > ");
> > * document.head.appendChild(script)
> > * var link = document.createElement("link");
> > * link.setAttribute("rel", "stylesheet");
> > * link.setAttribute("type", "text/css");
> > * link.setAttribute("href", "
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=MhWWj%2BwxeRxK3%2B3xpq4UqY%2FDOaL6WiDbLnvdr%2BRRSio%3D&reserved=0
> > ");
> > * document.head.appendChild(link);
> > * </inject_script>
> > */
> >
> > Then all the compiler needs to do is copy that JS into the
> appropriate
> > file. I suppose we could always prepend it to the .js file, but I
> think if
> > we wanted we could inject it into the html wrapper by copying the
> entire
> > contents in between <script></script> tags.
> >
> > The compiler would not have to parse anything, just copy like it
> currently
> > does. We would have to go and re-write all of the current
> inject_htmls,
> > although, as I said earlier, I think many inject_htmls should be
> replaced
> > by other mechanism like static initializers. The real need for
> > inject_html/inject_script is to make sure some external dependency
> has been
> > loaded so a class can initialize (as the various clss.prototype.foo
> get
> > interpreted). If the class just needs the dependency at runtime,
> load it
> > later in the code for the class. That makes it more PAYG as well.
> >
> > Of course, I could be wrong...
> > -Alex
> >
> > On 5/11/20, 9:18 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> >
> > I guess I could add
> >
> > <inject_script src=””/> and <inject_link href=””/> syntax which
> would
> > be easier to parse and then transpile that, similar to how it’s done
> today.
> > Before I go too crazy though, can someone remind me why outerHTML is
> evil?
> >
> > Thanks.
> >
> > From: Yishay Weiss<ma...@hotmail.com>
> > Sent: Monday, May 11, 2020 7:00 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> >
> > >What if we abandon "inject_html" and go with "inject_script"
> > instead? Then when adding to the html output, each >script would be
> > wrapped with a <script> tag, but for modules the code could be added
> to the
> > main module .js file.
> > I’m not sure about this. I think typically you inject a <link
> > href=”x”> for css and a <script src=”y”> for the js. How do you
> propose to
> > add those to the module js?
> >
> > On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > Hi Carlos, thanks. The issue is with inject_html in modules
> on IE,
> > dialogPolyfill.js just happened to be the target src here. I’ve been
> > searching the net for solutions on IE and I think the trick is to
> append
> > elements instead of changing the inner html. I see two options of
> > transpiling <inject_html> that would work on IE:
> >
> >
> > 1. Parse the <inject_html> contents in the compiler and
> create
> > js that would work for IE. Difficult.
> > 2. Replace each line in <inject_html> with dummy elements
> and
> > change their outerHTML to match each line contents. This one looks
> easier,
> > but I seem to remember a thread where we were trying to eliminate
> use of
> > outerHTML.
> >
> >
> > Any thoughts are welcome.
> >
> > From: Carlos Rovira<ma...@apache.org>
> > Sent: Monday, May 11, 2020 6:06 PM
> > To: Apache Royale Development<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Hi Yishay,
> >
> > talking without a huge analisys of the problem. I think Jewel
> > Alert works
> > ok in IE11 so that should mean dialogpolyfil is loading ok.
> if not
> > the case
> > something broke recently since I checked that in TDJ and
> other
> > apps we did.
> >
> > Anyway, the commit you state is just to give the support we
> > needed. I
> > didn't tested in IE11, so don't know if we support it.
> Normally
> > IE11 use to
> > require
> > some special way of writing the code for some particular
> things,
> > so I think
> > the way to solve this is:
> >
> > 1.- search in SOF or other sources how IE11 expect scripts
> to be
> > added
> > dynamically
> > 2.- upgrade the compiler code to use that way with that
> > considerations to
> > make it IE11 compatible and check if that works for IE11 and
> rest
> > of
> > browsers.
> >
> > sorry to not be able to say much more, but I'm these days
> with few
> > time
> >
> > Thanks
> >
> >
> >
> > El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<
> > yishayjobs@hotmail.com>)
> > escribió:
> >
> > > Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in
> > compiler code
> > > doesn’t work for IE11. Any ideas on how to fix this?
> > >
> > > From: Yishay Weiss<ma...@hotmail.com>
> > > Sent: Monday, May 11, 2020 4:52 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: RE: Modules in IE
> > >
> > > These lines in dialogPolyfill.as
> > >
> > > * <inject_html>
> > > * <script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > > "></script>
> > >
> > > get transpiled to
> > >
> > > document.head.innerHTML += '<script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > > "></script>'
> > >
> > > But that’s making IE11 fail in loading the module. It
> doesn’t
> > matter what
> > > the src is, IE will silently fail. For example, I’m
> getting the
> > same result
> > > if I replace the above with
> > >
> > > document.head.innerHTML += '<script></script>'
> > >
> > >
> > >
> > >
> > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > Sent: Sunday, May 10, 2020 7:35:55 PM
> > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > Does dialog-polyfill load correctly? Does it muck with the
> > window object?
> > >
> > > On 5/10/20, 9:13 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> > >
> > > Test1.js isn’t different, but Test1_deps.js is.
> > >
> > > diff --git
> "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > index 73eccbe..3e1a8a7 100644
> > > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > @@ -211,4 +211,4 @@
> > >
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > > ['org
> > > goog.addDependency('../../../XML.js', ['XML'], []);
> > >
> > > goog.require('Test1');
> > > -document.head.innerHTML += '<script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > > "></script<
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > > >>';document.head.innerHTM
> > > L += '<link rel="stylesheet" type="text/css" href="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=MhWWj%2BwxeRxK3%2B3xpq4UqY%2FDOaL6WiDbLnvdr%2BRRSio%3D&reserved=0
> > > ">';
> > > +
> > >
> > > From: Alex Harui<ma...@adobe.com.INVALID>
> > > Sent: Sunday, May 10, 2020 6:39 PM
> > > To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > Interesting. Just adding import shouldn't affect the
> > output. What is
> > > the difference between Test1.js with and without that
> import
> > statement?
> > >
> > > -Alex
> > >
> > > On 5/10/20, 8:31 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> > >
> > > I’ve narrowed it down to usage of
> mx.controls.Alert.
> > Test case is
> > > included in this issue [1].
> > >
> > > [1]
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=68mJrbzM53Hv%2BVOhisegFZAjSR%2BJktMnDOeUQoXKwqg%3D&reserved=0
> > >
> > > From: Alex Harui<ma...@adobe.com.INVALID>
> > > Sent: Thursday, May 7, 2020 10:35 PM
> > > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > I think you can verify by debugging in some other
> > browser and see
> > > if breakpoints get set.
> > >
> > > A common “bug” in Flex modules was to reference
> and link
> > the
> > > module class into the loading app. I have no idea what
> will
> > happen if you
> > > have such a situation in Royale. You can look at the
> loading
> > app’s
> > > link-report to see if the module (Test1) is linked in the
> app
> > and probably
> > > see if Test1.js is in the output of the app if you start
> clean
> > and do not
> > > compile the module.
> > >
> > > HTH,
> > > -Alex
> > >
> > > From: Yishay Weiss <yi...@hotmail.com>
> > > Reply-To: "dev@royale.apache.org" <
> dev@royale.apache.org
> > >
> > > Date: Thursday, May 7, 2020 at 12:26 PM
> > > To: "dev@royale.apache.org" <dev@royale.apache.org
> >
> > > Subject: RE: Modules in IE
> > >
> > > url is
> > >
> > >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/><file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/%3e1.js%3cfile:/C:/dev/RoyaleCom>>>>>>>
> > >
> > > I don’t see errors other than
> > >
> > > SEC7113: CSS was ignored due to mime type mismatch
> > >
> > > But I don’t think that’s it.
> > >
> > > I put a debugger; statement on the first line of
> the src
> > which
> > > never kicks.
> > >
> > >
> > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there
> any
> > errors
> > > loading and running it? Are the other Royale
> packages/classes
> > in the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or
> something
> > else
> > > creates a "window" property at the global window causing
> our
> > package lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com> wrote:
> > >
> > > In my example <script> element is there but
> it’s
> > never loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:
> aharui@adobe.com.INVALID>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE
> and
> > it worked.
> > > Does it work for you?
> > > In the debugger, window.Module and
> window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache
> property.
> > > In the DOM Explorer, there should be tons of
> > <script> tags in
> > > the head. Near the end of the list should be the script
> for the
> > .js file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works
> > without errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> > aharui@adobe.com.INVALID>
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: Alex Harui<ma...@adobe.com.INVALID>
> > > Sent: Wednesday, May 6, 2020 7:58 PM
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there
> any
> > errors
> > > loading and running it? Are the other Royale
> packages/classes
> > in the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or
> something
> > else
> > > creates a "window" property at the global window causing
> our
> > package lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com> wrote:
> > >
> > > In my example <script> element is there but
> it’s
> > never loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:
> aharui@adobe.com.INVALID>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE
> and
> > it worked.
> > > Does it work for you?
> > > In the debugger, window.Module and
> window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache
> property.
> > > In the DOM Explorer, there should be tons of
> > <script> tags in
> > > the head. Near the end of the list should be the script
> for the
> > .js file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works
> > without errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> > aharui@adobe.com.INVALID>
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: Alex Harui<ma...@adobe.com.INVALID>
> > > Sent: Sunday, May 10, 2020 7:36 PM
> > > Subject: Re: Modules in IE
> > >
> > > Does dialog-polyfill load correctly? Does it muck with the
> > window object?
> > >
> > > On 5/10/20, 9:13 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> > >
> > > Test1.js isn’t different, but Test1_deps.js is.
> > >
> > > diff --git
> "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > index 73eccbe..3e1a8a7 100644
> > > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > @@ -211,4 +211,4 @@
> > >
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > > ['org
> > > goog.addDependency('../../../XML.js', ['XML'], []);
> > >
> > > goog.require('Test1');
> > > -document.head.innerHTML += '<script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > > "></script<
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > > >>';document.head.innerHTM
> > > L += '<link rel="stylesheet" type="text/css" href="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=MhWWj%2BwxeRxK3%2B3xpq4UqY%2FDOaL6WiDbLnvdr%2BRRSio%3D&reserved=0
> > > ">';
> > > +
> > >
> > > From: Alex Harui<ma...@adobe.com.INVALID>
> > > Sent: Sunday, May 10, 2020 6:39 PM
> > > To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > Interesting. Just adding import shouldn't affect the
> > output. What is
> > > the difference between Test1.js with and without that
> import
> > statement?
> > >
> > > -Alex
> > >
> > > On 5/10/20, 8:31 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> > >
> > > I’ve narrowed it down to usage of
> mx.controls.Alert.
> > Test case is
> > > included in this issue [1].
> > >
> > > [1]
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=68mJrbzM53Hv%2BVOhisegFZAjSR%2BJktMnDOeUQoXKwqg%3D&reserved=0
> > >
> > > From: Alex Harui<ma...@adobe.com.INVALID>
> > > Sent: Thursday, May 7, 2020 10:35 PM
> > > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > I think you can verify by debugging in some other
> > browser and see
> > > if breakpoints get set.
> > >
> > > A common “bug” in Flex modules was to reference
> and link
> > the
> > > module class into the loading app. I have no idea what
> will
> > happen if you
> > > have such a situation in Royale. You can look at the
> loading
> > app’s
> > > link-report to see if the module (Test1) is linked in the
> app
> > and probably
> > > see if Test1.js is in the output of the app if you start
> clean
> > and do not
> > > compile the module.
> > >
> > > HTH,
> > > -Alex
> > >
> > > From: Yishay Weiss <yi...@hotmail.com>
> > > Reply-To: "dev@royale.apache.org" <
> dev@royale.apache.org
> > >
> > > Date: Thursday, May 7, 2020 at 12:26 PM
> > > To: "dev@royale.apache.org" <dev@royale.apache.org
> >
> > > Subject: RE: Modules in IE
> > >
> > > url is
> > >
> > >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentT<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/Royal<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>eComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>est/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>>>>>>
> > >
> > > I don’t see errors other than
> > >
> > > SEC7113: CSS was ignored due to mime type mismatch
> > >
> > > But I don’t think that’s it.
> > >
> > > I put a debugger; statement on the first line of
> the src
> > which
> > > never kicks.
> > >
> > >
> > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there
> any
> > errors
> > > loading and running it? Are the other Royale
> packages/classes
> > in the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or
> something
> > else
> > > creates a "window" property at the global window causing
> our
> > package lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com> wrote:
> > >
> > > In my example <script> element is there but
> it’s
> > never loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:
> aharui@adobe.com.INVALID>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE
> and
> > it worked.
> > > Does it work for you?
> > > In the debugger, window.Module and
> window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache
> property.
> > > In the DOM Explorer, there should be tons of
> > <script> tags in
> > > the head. Near the end of the list should be the script
> for the
> > .js file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works
> > without errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> > aharui@adobe.com.INVALID>
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: Alex Harui<ma...@adobe.com.INVALID>
> > > Sent: Wednesday, May 6, 2020 7:58 PM
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there
> any
> > errors
> > > loading and running it? Are the other Royale
> packages/classes
> > in the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or
> something
> > else
> > > creates a "window" property at the global window causing
> our
> > package lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com> wrote:
> > >
> > > In my example <script> element is there but
> it’s
> > never loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:
> aharui@adobe.com.INVALID>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE
> and
> > it worked.
> > > Does it work for you?
> > > In the debugger, window.Module and
> window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache
> property.
> > > In the DOM Explorer, there should be tons of
> > <script> tags in
> > > the head. Near the end of the list should be the script
> for the
> > .js file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works
> > without errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> > aharui@adobe.com.INVALID>
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > --
> > Carlos Rovira
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uQa7YC%2BnUiA99EK2Bp7Zt4XoGM83QGHud18jHOuiozQ%3D&reserved=0
> >
> >
> >
> >
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862253347&sdata=ut8lSfyDfOHTSPTY3R5j3LYFwOGV%2BTA9NurMwtvpxks%3D&reserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862253347&sdata=ut8lSfyDfOHTSPTY3R5j3LYFwOGV%2BTA9NurMwtvpxks%3D&reserved=0
> >*
>
>
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
RE: Modules in IE
Posted by Yishay Weiss <yi...@hotmail.com>.
We can re-insert this feature if backwards compatibility becomes a big enough issue. Looking forward, I agree with what you said before that we should encourage less use of this pattern rather than more.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, May 14, 2020 6:52 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
FWIW, It occurred to me that we could leave inject_html in addition to inject_script and just document that it doesn't work in modules and not use it in the framework.
Just a thought,
-Alex
On 5/14/20, 8:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
Sure, will wait.
Users will be required to change their inject_html annotations to inject_script similar to what was done here [1]
[1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fcommit%2F14322f16c3ce44e7a4bdd2f3dc80f60e30842bd0&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=m97rrA1IIlrrTKyE9nDFO9SfCh5q3SAHrMwpd1%2BnV00%3D&reserved=0
From: Piotr Zarzycki<ma...@gmail.com>
Sent: Thursday, May 14, 2020 5:56 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: Modules in IE
Please give me one more day more - Wait till Saturday. I would like to test
your changes tomorrow with our application, so I would not run into some
trouble with the next SDK update. As I understand the same name of the
branch applies also for compiler changes ?
czw., 14 maj 2020 o 16:51 Yishay Weiss <yi...@hotmail.com> napisał(a):
> I’ve implemented this idea in inject_script branches for compiler and
> as-js. If someone has time test those it would be very helpful. It works
> for my case. I’ll do some more basic testing and if there are no objections
> I’ll merge tomorrow. Thanks.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Monday, May 11, 2020 8:05 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> My idea wasn't quite that. It was to write the injection in JS instead of
> HTML. Here's a current inject_html from dialogPolyfill.as
>
> /**
> * <inject_html>
> * <script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=NRqG0jKqi9%2B4rZSOXkolO7OIKtAkzgrVJXhdzR%2B5l7I%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js%2522%253e%253c%2Fscript&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=2PlimX1AeQm4CV9LRsVZJnIxvP6zujyaOK09GLYSmrI%3D&reserved=0
> >>
> * <link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=Q52Eb7XLAV1cYR4iloI%2BQXL64XD9gwQYEFDydjOb7cg%3D&reserved=0
> ">
> * </inject_html>
> */
>
> I think if it was rewritten as:
>
> /**
> * <inject_script>
> * var script = document.createElement("script");
> * script.setAttribute("src", "
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=NRqG0jKqi9%2B4rZSOXkolO7OIKtAkzgrVJXhdzR%2B5l7I%3D&reserved=0
> ");
> * document.head.appendChild(script)
> * var link = document.createElement("link");
> * link.setAttribute("rel", "stylesheet");
> * link.setAttribute("type", "text/css");
> * link.setAttribute("href", "
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=MhWWj%2BwxeRxK3%2B3xpq4UqY%2FDOaL6WiDbLnvdr%2BRRSio%3D&reserved=0
> ");
> * document.head.appendChild(link);
> * </inject_script>
> */
>
> Then all the compiler needs to do is copy that JS into the appropriate
> file. I suppose we could always prepend it to the .js file, but I think if
> we wanted we could inject it into the html wrapper by copying the entire
> contents in between <script></script> tags.
>
> The compiler would not have to parse anything, just copy like it currently
> does. We would have to go and re-write all of the current inject_htmls,
> although, as I said earlier, I think many inject_htmls should be replaced
> by other mechanism like static initializers. The real need for
> inject_html/inject_script is to make sure some external dependency has been
> loaded so a class can initialize (as the various clss.prototype.foo get
> interpreted). If the class just needs the dependency at runtime, load it
> later in the code for the class. That makes it more PAYG as well.
>
> Of course, I could be wrong...
> -Alex
>
> On 5/11/20, 9:18 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I guess I could add
>
> <inject_script src=””/> and <inject_link href=””/> syntax which would
> be easier to parse and then transpile that, similar to how it’s done today.
> Before I go too crazy though, can someone remind me why outerHTML is evil?
>
> Thanks.
>
> From: Yishay Weiss<ma...@hotmail.com>
> Sent: Monday, May 11, 2020 7:00 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: RE: Modules in IE
>
>
> >What if we abandon "inject_html" and go with "inject_script"
> instead? Then when adding to the html output, each >script would be
> wrapped with a <script> tag, but for modules the code could be added to the
> main module .js file.
> I’m not sure about this. I think typically you inject a <link
> href=”x”> for css and a <script src=”y”> for the js. How do you propose to
> add those to the module js?
>
> On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Hi Carlos, thanks. The issue is with inject_html in modules on IE,
> dialogPolyfill.js just happened to be the target src here. I’ve been
> searching the net for solutions on IE and I think the trick is to append
> elements instead of changing the inner html. I see two options of
> transpiling <inject_html> that would work on IE:
>
>
> 1. Parse the <inject_html> contents in the compiler and create
> js that would work for IE. Difficult.
> 2. Replace each line in <inject_html> with dummy elements and
> change their outerHTML to match each line contents. This one looks easier,
> but I seem to remember a thread where we were trying to eliminate use of
> outerHTML.
>
>
> Any thoughts are welcome.
>
> From: Carlos Rovira<ma...@apache.org>
> Sent: Monday, May 11, 2020 6:06 PM
> To: Apache Royale Development<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Hi Yishay,
>
> talking without a huge analisys of the problem. I think Jewel
> Alert works
> ok in IE11 so that should mean dialogpolyfil is loading ok. if not
> the case
> something broke recently since I checked that in TDJ and other
> apps we did.
>
> Anyway, the commit you state is just to give the support we
> needed. I
> didn't tested in IE11, so don't know if we support it. Normally
> IE11 use to
> require
> some special way of writing the code for some particular things,
> so I think
> the way to solve this is:
>
> 1.- search in SOF or other sources how IE11 expect scripts to be
> added
> dynamically
> 2.- upgrade the compiler code to use that way with that
> considerations to
> make it IE11 compatible and check if that works for IE11 and rest
> of
> browsers.
>
> sorry to not be able to say much more, but I'm these days with few
> time
>
> Thanks
>
>
>
> El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<
> yishayjobs@hotmail.com>)
> escribió:
>
> > Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in
> compiler code
> > doesn’t work for IE11. Any ideas on how to fix this?
> >
> > From: Yishay Weiss<ma...@hotmail.com>
> > Sent: Monday, May 11, 2020 4:52 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > These lines in dialogPolyfill.as
> >
> > * <inject_html>
> > * <script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > "></script>
> >
> > get transpiled to
> >
> > document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > "></script>'
> >
> > But that’s making IE11 fail in loading the module. It doesn’t
> matter what
> > the src is, IE will silently fail. For example, I’m getting the
> same result
> > if I replace the above with
> >
> > document.head.innerHTML += '<script></script>'
> >
> >
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 7:35:55 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Does dialog-polyfill load correctly? Does it muck with the
> window object?
> >
> > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > Test1.js isn’t different, but Test1_deps.js is.
> >
> > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > index 73eccbe..3e1a8a7 100644
> > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > @@ -211,4 +211,4 @@
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > ['org
> > goog.addDependency('../../../XML.js', ['XML'], []);
> >
> > goog.require('Test1');
> > -document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > "></script<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > >>';document.head.innerHTM
> > L += '<link rel="stylesheet" type="text/css" href="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=MhWWj%2BwxeRxK3%2B3xpq4UqY%2FDOaL6WiDbLnvdr%2BRRSio%3D&reserved=0
> > ">';
> > +
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 6:39 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Interesting. Just adding import shouldn't affect the
> output. What is
> > the difference between Test1.js with and without that import
> statement?
> >
> > -Alex
> >
> > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > I’ve narrowed it down to usage of mx.controls.Alert.
> Test case is
> > included in this issue [1].
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=68mJrbzM53Hv%2BVOhisegFZAjSR%2BJktMnDOeUQoXKwqg%3D&reserved=0
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Thursday, May 7, 2020 10:35 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I think you can verify by debugging in some other
> browser and see
> > if breakpoints get set.
> >
> > A common “bug” in Flex modules was to reference and link
> the
> > module class into the loading app. I have no idea what will
> happen if you
> > have such a situation in Royale. You can look at the loading
> app’s
> > link-report to see if the module (Test1) is linked in the app
> and probably
> > see if Test1.js is in the output of the app if you start clean
> and do not
> > compile the module.
> >
> > HTH,
> > -Alex
> >
> > From: Yishay Weiss <yi...@hotmail.com>
> > Reply-To: "dev@royale.apache.org" <dev@royale.apache.org
> >
> > Date: Thursday, May 7, 2020 at 12:26 PM
> > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > url is
> >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/><file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/%3e1.js%3cfile:/C:/dev/RoyaleCom>>>>>>>
> >
> > I don’t see errors other than
> >
> > SEC7113: CSS was ignored due to mime type mismatch
> >
> > But I don’t think that’s it.
> >
> > I put a debugger; statement on the first line of the src
> which
> > never kicks.
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any
> errors
> > loading and running it? Are the other Royale packages/classes
> in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something
> else
> > creates a "window" property at the global window causing our
> package lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com> wrote:
> >
> > In my example <script> element is there but it’s
> never loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and
> it worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of
> <script> tags in
> > the head. Near the end of the list should be the script for the
> .js file
> > for the module.
> > Do you see any exceptions? ModuleExample works
> without errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58 PM
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any
> errors
> > loading and running it? Are the other Royale packages/classes
> in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something
> else
> > creates a "window" property at the global window causing our
> package lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com> wrote:
> >
> > In my example <script> element is there but it’s
> never loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and
> it worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of
> <script> tags in
> > the head. Near the end of the list should be the script for the
> .js file
> > for the module.
> > Do you see any exceptions? ModuleExample works
> without errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 7:36 PM
> > Subject: Re: Modules in IE
> >
> > Does dialog-polyfill load correctly? Does it muck with the
> window object?
> >
> > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > Test1.js isn’t different, but Test1_deps.js is.
> >
> > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > index 73eccbe..3e1a8a7 100644
> > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > @@ -211,4 +211,4 @@
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > ['org
> > goog.addDependency('../../../XML.js', ['XML'], []);
> >
> > goog.require('Test1');
> > -document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > "></script<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > >>';document.head.innerHTM
> > L += '<link rel="stylesheet" type="text/css" href="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=MhWWj%2BwxeRxK3%2B3xpq4UqY%2FDOaL6WiDbLnvdr%2BRRSio%3D&reserved=0
> > ">';
> > +
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 6:39 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Interesting. Just adding import shouldn't affect the
> output. What is
> > the difference between Test1.js with and without that import
> statement?
> >
> > -Alex
> >
> > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > I’ve narrowed it down to usage of mx.controls.Alert.
> Test case is
> > included in this issue [1].
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=68mJrbzM53Hv%2BVOhisegFZAjSR%2BJktMnDOeUQoXKwqg%3D&reserved=0
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Thursday, May 7, 2020 10:35 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I think you can verify by debugging in some other
> browser and see
> > if breakpoints get set.
> >
> > A common “bug” in Flex modules was to reference and link
> the
> > module class into the loading app. I have no idea what will
> happen if you
> > have such a situation in Royale. You can look at the loading
> app’s
> > link-report to see if the module (Test1) is linked in the app
> and probably
> > see if Test1.js is in the output of the app if you start clean
> and do not
> > compile the module.
> >
> > HTH,
> > -Alex
> >
> > From: Yishay Weiss <yi...@hotmail.com>
> > Reply-To: "dev@royale.apache.org" <dev@royale.apache.org
> >
> > Date: Thursday, May 7, 2020 at 12:26 PM
> > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > url is
> >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentT<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/Royal<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>eComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>est/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>>>>>>
> >
> > I don’t see errors other than
> >
> > SEC7113: CSS was ignored due to mime type mismatch
> >
> > But I don’t think that’s it.
> >
> > I put a debugger; statement on the first line of the src
> which
> > never kicks.
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any
> errors
> > loading and running it? Are the other Royale packages/classes
> in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something
> else
> > creates a "window" property at the global window causing our
> package lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com> wrote:
> >
> > In my example <script> element is there but it’s
> never loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and
> it worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of
> <script> tags in
> > the head. Near the end of the list should be the script for the
> .js file
> > for the module.
> > Do you see any exceptions? ModuleExample works
> without errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58 PM
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any
> errors
> > loading and running it? Are the other Royale packages/classes
> in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something
> else
> > creates a "window" property at the global window causing our
> package lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com> wrote:
> >
> > In my example <script> element is there but it’s
> never loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and
> it worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of
> <script> tags in
> > the head. Near the end of the list should be the script for the
> .js file
> > for the module.
> > Do you see any exceptions? ModuleExample works
> without errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uQa7YC%2BnUiA99EK2Bp7Zt4XoGM83QGHud18jHOuiozQ%3D&reserved=0
>
>
>
>
>
>
>
--
Piotr Zarzycki
Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862253347&sdata=ut8lSfyDfOHTSPTY3R5j3LYFwOGV%2BTA9NurMwtvpxks%3D&reserved=0
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862253347&sdata=ut8lSfyDfOHTSPTY3R5j3LYFwOGV%2BTA9NurMwtvpxks%3D&reserved=0>*
Re: Modules in IE
Posted by Alex Harui <ah...@adobe.com.INVALID>.
FWIW, It occurred to me that we could leave inject_html in addition to inject_script and just document that it doesn't work in modules and not use it in the framework.
Just a thought,
-Alex
On 5/14/20, 8:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
Sure, will wait.
Users will be required to change their inject_html annotations to inject_script similar to what was done here [1]
[1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fcommit%2F14322f16c3ce44e7a4bdd2f3dc80f60e30842bd0&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=m97rrA1IIlrrTKyE9nDFO9SfCh5q3SAHrMwpd1%2BnV00%3D&reserved=0
From: Piotr Zarzycki<ma...@gmail.com>
Sent: Thursday, May 14, 2020 5:56 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: Modules in IE
Please give me one more day more - Wait till Saturday. I would like to test
your changes tomorrow with our application, so I would not run into some
trouble with the next SDK update. As I understand the same name of the
branch applies also for compiler changes ?
czw., 14 maj 2020 o 16:51 Yishay Weiss <yi...@hotmail.com> napisał(a):
> I’ve implemented this idea in inject_script branches for compiler and
> as-js. If someone has time test those it would be very helpful. It works
> for my case. I’ll do some more basic testing and if there are no objections
> I’ll merge tomorrow. Thanks.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Monday, May 11, 2020 8:05 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> My idea wasn't quite that. It was to write the injection in JS instead of
> HTML. Here's a current inject_html from dialogPolyfill.as
>
> /**
> * <inject_html>
> * <script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=NRqG0jKqi9%2B4rZSOXkolO7OIKtAkzgrVJXhdzR%2B5l7I%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js%2522%253e%253c%2Fscript&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=2PlimX1AeQm4CV9LRsVZJnIxvP6zujyaOK09GLYSmrI%3D&reserved=0
> >>
> * <link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=Q52Eb7XLAV1cYR4iloI%2BQXL64XD9gwQYEFDydjOb7cg%3D&reserved=0
> ">
> * </inject_html>
> */
>
> I think if it was rewritten as:
>
> /**
> * <inject_script>
> * var script = document.createElement("script");
> * script.setAttribute("src", "
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862233431&sdata=NRqG0jKqi9%2B4rZSOXkolO7OIKtAkzgrVJXhdzR%2B5l7I%3D&reserved=0
> ");
> * document.head.appendChild(script)
> * var link = document.createElement("link");
> * link.setAttribute("rel", "stylesheet");
> * link.setAttribute("type", "text/css");
> * link.setAttribute("href", "
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=MhWWj%2BwxeRxK3%2B3xpq4UqY%2FDOaL6WiDbLnvdr%2BRRSio%3D&reserved=0
> ");
> * document.head.appendChild(link);
> * </inject_script>
> */
>
> Then all the compiler needs to do is copy that JS into the appropriate
> file. I suppose we could always prepend it to the .js file, but I think if
> we wanted we could inject it into the html wrapper by copying the entire
> contents in between <script></script> tags.
>
> The compiler would not have to parse anything, just copy like it currently
> does. We would have to go and re-write all of the current inject_htmls,
> although, as I said earlier, I think many inject_htmls should be replaced
> by other mechanism like static initializers. The real need for
> inject_html/inject_script is to make sure some external dependency has been
> loaded so a class can initialize (as the various clss.prototype.foo get
> interpreted). If the class just needs the dependency at runtime, load it
> later in the code for the class. That makes it more PAYG as well.
>
> Of course, I could be wrong...
> -Alex
>
> On 5/11/20, 9:18 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I guess I could add
>
> <inject_script src=””/> and <inject_link href=””/> syntax which would
> be easier to parse and then transpile that, similar to how it’s done today.
> Before I go too crazy though, can someone remind me why outerHTML is evil?
>
> Thanks.
>
> From: Yishay Weiss<ma...@hotmail.com>
> Sent: Monday, May 11, 2020 7:00 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: RE: Modules in IE
>
>
> >What if we abandon "inject_html" and go with "inject_script"
> instead? Then when adding to the html output, each >script would be
> wrapped with a <script> tag, but for modules the code could be added to the
> main module .js file.
> I’m not sure about this. I think typically you inject a <link
> href=”x”> for css and a <script src=”y”> for the js. How do you propose to
> add those to the module js?
>
> On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Hi Carlos, thanks. The issue is with inject_html in modules on IE,
> dialogPolyfill.js just happened to be the target src here. I’ve been
> searching the net for solutions on IE and I think the trick is to append
> elements instead of changing the inner html. I see two options of
> transpiling <inject_html> that would work on IE:
>
>
> 1. Parse the <inject_html> contents in the compiler and create
> js that would work for IE. Difficult.
> 2. Replace each line in <inject_html> with dummy elements and
> change their outerHTML to match each line contents. This one looks easier,
> but I seem to remember a thread where we were trying to eliminate use of
> outerHTML.
>
>
> Any thoughts are welcome.
>
> From: Carlos Rovira<ma...@apache.org>
> Sent: Monday, May 11, 2020 6:06 PM
> To: Apache Royale Development<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Hi Yishay,
>
> talking without a huge analisys of the problem. I think Jewel
> Alert works
> ok in IE11 so that should mean dialogpolyfil is loading ok. if not
> the case
> something broke recently since I checked that in TDJ and other
> apps we did.
>
> Anyway, the commit you state is just to give the support we
> needed. I
> didn't tested in IE11, so don't know if we support it. Normally
> IE11 use to
> require
> some special way of writing the code for some particular things,
> so I think
> the way to solve this is:
>
> 1.- search in SOF or other sources how IE11 expect scripts to be
> added
> dynamically
> 2.- upgrade the compiler code to use that way with that
> considerations to
> make it IE11 compatible and check if that works for IE11 and rest
> of
> browsers.
>
> sorry to not be able to say much more, but I'm these days with few
> time
>
> Thanks
>
>
>
> El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<
> yishayjobs@hotmail.com>)
> escribió:
>
> > Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in
> compiler code
> > doesn’t work for IE11. Any ideas on how to fix this?
> >
> > From: Yishay Weiss<ma...@hotmail.com>
> > Sent: Monday, May 11, 2020 4:52 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > These lines in dialogPolyfill.as
> >
> > * <inject_html>
> > * <script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > "></script>
> >
> > get transpiled to
> >
> > document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > "></script>'
> >
> > But that’s making IE11 fail in loading the module. It doesn’t
> matter what
> > the src is, IE will silently fail. For example, I’m getting the
> same result
> > if I replace the above with
> >
> > document.head.innerHTML += '<script></script>'
> >
> >
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 7:35:55 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Does dialog-polyfill load correctly? Does it muck with the
> window object?
> >
> > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > Test1.js isn’t different, but Test1_deps.js is.
> >
> > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > index 73eccbe..3e1a8a7 100644
> > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > @@ -211,4 +211,4 @@
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > ['org
> > goog.addDependency('../../../XML.js', ['XML'], []);
> >
> > goog.require('Test1');
> > -document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > "></script<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > >>';document.head.innerHTM
> > L += '<link rel="stylesheet" type="text/css" href="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=MhWWj%2BwxeRxK3%2B3xpq4UqY%2FDOaL6WiDbLnvdr%2BRRSio%3D&reserved=0
> > ">';
> > +
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 6:39 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Interesting. Just adding import shouldn't affect the
> output. What is
> > the difference between Test1.js with and without that import
> statement?
> >
> > -Alex
> >
> > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > I’ve narrowed it down to usage of mx.controls.Alert.
> Test case is
> > included in this issue [1].
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=68mJrbzM53Hv%2BVOhisegFZAjSR%2BJktMnDOeUQoXKwqg%3D&reserved=0
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Thursday, May 7, 2020 10:35 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I think you can verify by debugging in some other
> browser and see
> > if breakpoints get set.
> >
> > A common “bug” in Flex modules was to reference and link
> the
> > module class into the loading app. I have no idea what will
> happen if you
> > have such a situation in Royale. You can look at the loading
> app’s
> > link-report to see if the module (Test1) is linked in the app
> and probably
> > see if Test1.js is in the output of the app if you start clean
> and do not
> > compile the module.
> >
> > HTH,
> > -Alex
> >
> > From: Yishay Weiss <yi...@hotmail.com>
> > Reply-To: "dev@royale.apache.org" <dev@royale.apache.org
> >
> > Date: Thursday, May 7, 2020 at 12:26 PM
> > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > url is
> >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>>>>>>
> >
> > I don’t see errors other than
> >
> > SEC7113: CSS was ignored due to mime type mismatch
> >
> > But I don’t think that’s it.
> >
> > I put a debugger; statement on the first line of the src
> which
> > never kicks.
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any
> errors
> > loading and running it? Are the other Royale packages/classes
> in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something
> else
> > creates a "window" property at the global window causing our
> package lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com> wrote:
> >
> > In my example <script> element is there but it’s
> never loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and
> it worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of
> <script> tags in
> > the head. Near the end of the list should be the script for the
> .js file
> > for the module.
> > Do you see any exceptions? ModuleExample works
> without errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58 PM
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any
> errors
> > loading and running it? Are the other Royale packages/classes
> in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something
> else
> > creates a "window" property at the global window causing our
> package lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com> wrote:
> >
> > In my example <script> element is there but it’s
> never loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and
> it worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of
> <script> tags in
> > the head. Near the end of the list should be the script for the
> .js file
> > for the module.
> > Do you see any exceptions? ModuleExample works
> without errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 7:36 PM
> > Subject: Re: Modules in IE
> >
> > Does dialog-polyfill load correctly? Does it muck with the
> window object?
> >
> > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > Test1.js isn’t different, but Test1_deps.js is.
> >
> > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > index 73eccbe..3e1a8a7 100644
> > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > @@ -211,4 +211,4 @@
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > ['org
> > goog.addDependency('../../../XML.js', ['XML'], []);
> >
> > goog.require('Test1');
> > -document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > "></script<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uxUDPc0%2BepDZvox9qzSNTy7KHn1UiMY4YEVjVUdO9CU%3D&reserved=0
> > >>';document.head.innerHTM
> > L += '<link rel="stylesheet" type="text/css" href="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=MhWWj%2BwxeRxK3%2B3xpq4UqY%2FDOaL6WiDbLnvdr%2BRRSio%3D&reserved=0
> > ">';
> > +
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 6:39 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Interesting. Just adding import shouldn't affect the
> output. What is
> > the difference between Test1.js with and without that import
> statement?
> >
> > -Alex
> >
> > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > I’ve narrowed it down to usage of mx.controls.Alert.
> Test case is
> > included in this issue [1].
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=68mJrbzM53Hv%2BVOhisegFZAjSR%2BJktMnDOeUQoXKwqg%3D&reserved=0
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Thursday, May 7, 2020 10:35 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I think you can verify by debugging in some other
> browser and see
> > if breakpoints get set.
> >
> > A common “bug” in Flex modules was to reference and link
> the
> > module class into the loading app. I have no idea what will
> happen if you
> > have such a situation in Royale. You can look at the loading
> app’s
> > link-report to see if the module (Test1) is linked in the app
> and probably
> > see if Test1.js is in the output of the app if you start clean
> and do not
> > compile the module.
> >
> > HTH,
> > -Alex
> >
> > From: Yishay Weiss <yi...@hotmail.com>
> > Reply-To: "dev@royale.apache.org" <dev@royale.apache.org
> >
> > Date: Thursday, May 7, 2020 at 12:26 PM
> > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > url is
> >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentT<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>est/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>>>>>>
> >
> > I don’t see errors other than
> >
> > SEC7113: CSS was ignored due to mime type mismatch
> >
> > But I don’t think that’s it.
> >
> > I put a debugger; statement on the first line of the src
> which
> > never kicks.
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any
> errors
> > loading and running it? Are the other Royale packages/classes
> in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something
> else
> > creates a "window" property at the global window causing our
> package lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com> wrote:
> >
> > In my example <script> element is there but it’s
> never loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and
> it worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of
> <script> tags in
> > the head. Near the end of the list should be the script for the
> .js file
> > for the module.
> > Do you see any exceptions? ModuleExample works
> without errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58 PM
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any
> errors
> > loading and running it? Are the other Royale packages/classes
> in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something
> else
> > creates a "window" property at the global window causing our
> package lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com> wrote:
> >
> > In my example <script> element is there but it’s
> never loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and
> it worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of
> <script> tags in
> > the head. Near the end of the list should be the script for the
> .js file
> > for the module.
> > Do you see any exceptions? ModuleExample works
> without errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862243384&sdata=uQa7YC%2BnUiA99EK2Bp7Zt4XoGM83QGHud18jHOuiozQ%3D&reserved=0
>
>
>
>
>
>
>
--
Piotr Zarzycki
Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862253347&sdata=ut8lSfyDfOHTSPTY3R5j3LYFwOGV%2BTA9NurMwtvpxks%3D&reserved=0
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd503684165ad4f18cda908d7f817ab3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250652862253347&sdata=ut8lSfyDfOHTSPTY3R5j3LYFwOGV%2BTA9NurMwtvpxks%3D&reserved=0>*
RE: Modules in IE
Posted by Yishay Weiss <yi...@hotmail.com>.
Sure, will wait.
Users will be required to change their inject_html annotations to inject_script similar to what was done here [1]
[1] https://github.com/apache/royale-asjs/commit/14322f16c3ce44e7a4bdd2f3dc80f60e30842bd0
From: Piotr Zarzycki<ma...@gmail.com>
Sent: Thursday, May 14, 2020 5:56 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: Modules in IE
Please give me one more day more - Wait till Saturday. I would like to test
your changes tomorrow with our application, so I would not run into some
trouble with the next SDK update. As I understand the same name of the
branch applies also for compiler changes ?
czw., 14 maj 2020 o 16:51 Yishay Weiss <yi...@hotmail.com> napisał(a):
> I’ve implemented this idea in inject_script branches for compiler and
> as-js. If someone has time test those it would be very helpful. It works
> for my case. I’ll do some more basic testing and if there are no objections
> I’ll merge tomorrow. Thanks.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Monday, May 11, 2020 8:05 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> My idea wasn't quite that. It was to write the injection in JS instead of
> HTML. Here's a current inject_html from dialogPolyfill.as
>
> /**
> * <inject_html>
> * <script src="
> https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js
> "></script<
> https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js%22%3e%3c/script
> >>
> * <link rel="stylesheet" type="text/css" href="
> https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.css
> ">
> * </inject_html>
> */
>
> I think if it was rewritten as:
>
> /**
> * <inject_script>
> * var script = document.createElement("script");
> * script.setAttribute("src", "
> https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js
> ");
> * document.head.appendChild(script)
> * var link = document.createElement("link");
> * link.setAttribute("rel", "stylesheet");
> * link.setAttribute("type", "text/css");
> * link.setAttribute("href", "
> https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.css
> ");
> * document.head.appendChild(link);
> * </inject_script>
> */
>
> Then all the compiler needs to do is copy that JS into the appropriate
> file. I suppose we could always prepend it to the .js file, but I think if
> we wanted we could inject it into the html wrapper by copying the entire
> contents in between <script></script> tags.
>
> The compiler would not have to parse anything, just copy like it currently
> does. We would have to go and re-write all of the current inject_htmls,
> although, as I said earlier, I think many inject_htmls should be replaced
> by other mechanism like static initializers. The real need for
> inject_html/inject_script is to make sure some external dependency has been
> loaded so a class can initialize (as the various clss.prototype.foo get
> interpreted). If the class just needs the dependency at runtime, load it
> later in the code for the class. That makes it more PAYG as well.
>
> Of course, I could be wrong...
> -Alex
>
> On 5/11/20, 9:18 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I guess I could add
>
> <inject_script src=””/> and <inject_link href=””/> syntax which would
> be easier to parse and then transpile that, similar to how it’s done today.
> Before I go too crazy though, can someone remind me why outerHTML is evil?
>
> Thanks.
>
> From: Yishay Weiss<ma...@hotmail.com>
> Sent: Monday, May 11, 2020 7:00 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: RE: Modules in IE
>
>
> >What if we abandon "inject_html" and go with "inject_script"
> instead? Then when adding to the html output, each >script would be
> wrapped with a <script> tag, but for modules the code could be added to the
> main module .js file.
> I’m not sure about this. I think typically you inject a <link
> href=”x”> for css and a <script src=”y”> for the js. How do you propose to
> add those to the module js?
>
> On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Hi Carlos, thanks. The issue is with inject_html in modules on IE,
> dialogPolyfill.js just happened to be the target src here. I’ve been
> searching the net for solutions on IE and I think the trick is to append
> elements instead of changing the inner html. I see two options of
> transpiling <inject_html> that would work on IE:
>
>
> 1. Parse the <inject_html> contents in the compiler and create
> js that would work for IE. Difficult.
> 2. Replace each line in <inject_html> with dummy elements and
> change their outerHTML to match each line contents. This one looks easier,
> but I seem to remember a thread where we were trying to eliminate use of
> outerHTML.
>
>
> Any thoughts are welcome.
>
> From: Carlos Rovira<ma...@apache.org>
> Sent: Monday, May 11, 2020 6:06 PM
> To: Apache Royale Development<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Hi Yishay,
>
> talking without a huge analisys of the problem. I think Jewel
> Alert works
> ok in IE11 so that should mean dialogpolyfil is loading ok. if not
> the case
> something broke recently since I checked that in TDJ and other
> apps we did.
>
> Anyway, the commit you state is just to give the support we
> needed. I
> didn't tested in IE11, so don't know if we support it. Normally
> IE11 use to
> require
> some special way of writing the code for some particular things,
> so I think
> the way to solve this is:
>
> 1.- search in SOF or other sources how IE11 expect scripts to be
> added
> dynamically
> 2.- upgrade the compiler code to use that way with that
> considerations to
> make it IE11 compatible and check if that works for IE11 and rest
> of
> browsers.
>
> sorry to not be able to say much more, but I'm these days with few
> time
>
> Thanks
>
>
>
> El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<
> yishayjobs@hotmail.com>)
> escribió:
>
> > Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in
> compiler code
> > doesn’t work for IE11. Any ideas on how to fix this?
> >
> > From: Yishay Weiss<ma...@hotmail.com>
> > Sent: Monday, May 11, 2020 4:52 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > These lines in dialogPolyfill.as
> >
> > * <inject_html>
> > * <script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324237150&sdata=mXiJMCztzMYBH6D6LM0%2Bdv2m4gFmFAoqpC%2FTVmjbn8g%3D&reserved=0
> > "></script>
> >
> > get transpiled to
> >
> > document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324237150&sdata=mXiJMCztzMYBH6D6LM0%2Bdv2m4gFmFAoqpC%2FTVmjbn8g%3D&reserved=0
> > "></script>'
> >
> > But that’s making IE11 fail in loading the module. It doesn’t
> matter what
> > the src is, IE will silently fail. For example, I’m getting the
> same result
> > if I replace the above with
> >
> > document.head.innerHTML += '<script></script>'
> >
> >
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 7:35:55 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Does dialog-polyfill load correctly? Does it muck with the
> window object?
> >
> > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > Test1.js isn’t different, but Test1_deps.js is.
> >
> > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > index 73eccbe..3e1a8a7 100644
> > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > @@ -211,4 +211,4 @@
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > ['org
> > goog.addDependency('../../../XML.js', ['XML'], []);
> >
> > goog.require('Test1');
> > -document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324237150&sdata=mXiJMCztzMYBH6D6LM0%2Bdv2m4gFmFAoqpC%2FTVmjbn8g%3D&reserved=0
> > "></script<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324237150&sdata=mXiJMCztzMYBH6D6LM0%2Bdv2m4gFmFAoqpC%2FTVmjbn8g%3D&reserved=0
> > >>';document.head.innerHTM
> > L += '<link rel="stylesheet" type="text/css" href="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=AiwgqYg2zTmgRs%2BzC3B82UOeIyedm9L6%2BS6%2FzkGKL0A%3D&reserved=0
> > ">';
> > +
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 6:39 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Interesting. Just adding import shouldn't affect the
> output. What is
> > the difference between Test1.js with and without that import
> statement?
> >
> > -Alex
> >
> > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > I’ve narrowed it down to usage of mx.controls.Alert.
> Test case is
> > included in this issue [1].
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=5XnYhvhgfJsonuIf0fHF%2FSSEDbgiow1Tbh345oQ7aC0%3D&reserved=0
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Thursday, May 7, 2020 10:35 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I think you can verify by debugging in some other
> browser and see
> > if breakpoints get set.
> >
> > A common “bug” in Flex modules was to reference and link
> the
> > module class into the loading app. I have no idea what will
> happen if you
> > have such a situation in Royale. You can look at the loading
> app’s
> > link-report to see if the module (Test1) is linked in the app
> and probably
> > see if Test1.js is in the output of the app if you start clean
> and do not
> > compile the module.
> >
> > HTH,
> > -Alex
> >
> > From: Yishay Weiss <yi...@hotmail.com>
> > Reply-To: "dev@royale.apache.org" <dev@royale.apache.org
> >
> > Date: Thursday, May 7, 2020 at 12:26 PM
> > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > url is
> >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>>>>>>
> >
> > I don’t see errors other than
> >
> > SEC7113: CSS was ignored due to mime type mismatch
> >
> > But I don’t think that’s it.
> >
> > I put a debugger; statement on the first line of the src
> which
> > never kicks.
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any
> errors
> > loading and running it? Are the other Royale packages/classes
> in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something
> else
> > creates a "window" property at the global window causing our
> package lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com> wrote:
> >
> > In my example <script> element is there but it’s
> never loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and
> it worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of
> <script> tags in
> > the head. Near the end of the list should be the script for the
> .js file
> > for the module.
> > Do you see any exceptions? ModuleExample works
> without errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58 PM
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any
> errors
> > loading and running it? Are the other Royale packages/classes
> in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something
> else
> > creates a "window" property at the global window causing our
> package lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com> wrote:
> >
> > In my example <script> element is there but it’s
> never loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and
> it worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of
> <script> tags in
> > the head. Near the end of the list should be the script for the
> .js file
> > for the module.
> > Do you see any exceptions? ModuleExample works
> without errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 7:36 PM
> > Subject: Re: Modules in IE
> >
> > Does dialog-polyfill load correctly? Does it muck with the
> window object?
> >
> > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > Test1.js isn’t different, but Test1_deps.js is.
> >
> > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > index 73eccbe..3e1a8a7 100644
> > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > @@ -211,4 +211,4 @@
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > ['org
> > goog.addDependency('../../../XML.js', ['XML'], []);
> >
> > goog.require('Test1');
> > -document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=B8KlNfzVS6I6U8V%2Bj6EOYDSjsxWPpuhGJ98XYfi%2ByEM%3D&reserved=0
> > "></script<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=B8KlNfzVS6I6U8V%2Bj6EOYDSjsxWPpuhGJ98XYfi%2ByEM%3D&reserved=0
> > >>';document.head.innerHTM
> > L += '<link rel="stylesheet" type="text/css" href="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=AiwgqYg2zTmgRs%2BzC3B82UOeIyedm9L6%2BS6%2FzkGKL0A%3D&reserved=0
> > ">';
> > +
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 6:39 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Interesting. Just adding import shouldn't affect the
> output. What is
> > the difference between Test1.js with and without that import
> statement?
> >
> > -Alex
> >
> > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > I’ve narrowed it down to usage of mx.controls.Alert.
> Test case is
> > included in this issue [1].
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=5XnYhvhgfJsonuIf0fHF%2FSSEDbgiow1Tbh345oQ7aC0%3D&reserved=0
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Thursday, May 7, 2020 10:35 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I think you can verify by debugging in some other
> browser and see
> > if breakpoints get set.
> >
> > A common “bug” in Flex modules was to reference and link
> the
> > module class into the loading app. I have no idea what will
> happen if you
> > have such a situation in Royale. You can look at the loading
> app’s
> > link-report to see if the module (Test1) is linked in the app
> and probably
> > see if Test1.js is in the output of the app if you start clean
> and do not
> > compile the module.
> >
> > HTH,
> > -Alex
> >
> > From: Yishay Weiss <yi...@hotmail.com>
> > Reply-To: "dev@royale.apache.org" <dev@royale.apache.org
> >
> > Date: Thursday, May 7, 2020 at 12:26 PM
> > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > url is
> >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentT<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>est/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>>>>>>
> >
> > I don’t see errors other than
> >
> > SEC7113: CSS was ignored due to mime type mismatch
> >
> > But I don’t think that’s it.
> >
> > I put a debugger; statement on the first line of the src
> which
> > never kicks.
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any
> errors
> > loading and running it? Are the other Royale packages/classes
> in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something
> else
> > creates a "window" property at the global window causing our
> package lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com> wrote:
> >
> > In my example <script> element is there but it’s
> never loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and
> it worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of
> <script> tags in
> > the head. Near the end of the list should be the script for the
> .js file
> > for the module.
> > Do you see any exceptions? ModuleExample works
> without errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58 PM
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any
> errors
> > loading and running it? Are the other Royale packages/classes
> in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something
> else
> > creates a "window" property at the global window causing our
> package lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com> wrote:
> >
> > In my example <script> element is there but it’s
> never loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and
> it worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of
> <script> tags in
> > the head. Near the end of the list should be the script for the
> .js file
> > for the module.
> > Do you see any exceptions? ModuleExample works
> without errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=oEuPO1QRYw31eRbzyd%2Bzqf1zHAH%2FUBX5B41zvuq8ZQs%3D&reserved=0
>
>
>
>
>
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Modules in IE
Posted by Piotr Zarzycki <pi...@gmail.com>.
Please give me one more day more - Wait till Saturday. I would like to test
your changes tomorrow with our application, so I would not run into some
trouble with the next SDK update. As I understand the same name of the
branch applies also for compiler changes ?
czw., 14 maj 2020 o 16:51 Yishay Weiss <yi...@hotmail.com> napisał(a):
> I’ve implemented this idea in inject_script branches for compiler and
> as-js. If someone has time test those it would be very helpful. It works
> for my case. I’ll do some more basic testing and if there are no objections
> I’ll merge tomorrow. Thanks.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Monday, May 11, 2020 8:05 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> My idea wasn't quite that. It was to write the injection in JS instead of
> HTML. Here's a current inject_html from dialogPolyfill.as
>
> /**
> * <inject_html>
> * <script src="
> https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js
> "></script<
> https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js%22%3e%3c/script
> >>
> * <link rel="stylesheet" type="text/css" href="
> https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.css
> ">
> * </inject_html>
> */
>
> I think if it was rewritten as:
>
> /**
> * <inject_script>
> * var script = document.createElement("script");
> * script.setAttribute("src", "
> https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js
> ");
> * document.head.appendChild(script)
> * var link = document.createElement("link");
> * link.setAttribute("rel", "stylesheet");
> * link.setAttribute("type", "text/css");
> * link.setAttribute("href", "
> https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.css
> ");
> * document.head.appendChild(link);
> * </inject_script>
> */
>
> Then all the compiler needs to do is copy that JS into the appropriate
> file. I suppose we could always prepend it to the .js file, but I think if
> we wanted we could inject it into the html wrapper by copying the entire
> contents in between <script></script> tags.
>
> The compiler would not have to parse anything, just copy like it currently
> does. We would have to go and re-write all of the current inject_htmls,
> although, as I said earlier, I think many inject_htmls should be replaced
> by other mechanism like static initializers. The real need for
> inject_html/inject_script is to make sure some external dependency has been
> loaded so a class can initialize (as the various clss.prototype.foo get
> interpreted). If the class just needs the dependency at runtime, load it
> later in the code for the class. That makes it more PAYG as well.
>
> Of course, I could be wrong...
> -Alex
>
> On 5/11/20, 9:18 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I guess I could add
>
> <inject_script src=””/> and <inject_link href=””/> syntax which would
> be easier to parse and then transpile that, similar to how it’s done today.
> Before I go too crazy though, can someone remind me why outerHTML is evil?
>
> Thanks.
>
> From: Yishay Weiss<ma...@hotmail.com>
> Sent: Monday, May 11, 2020 7:00 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: RE: Modules in IE
>
>
> >What if we abandon "inject_html" and go with "inject_script"
> instead? Then when adding to the html output, each >script would be
> wrapped with a <script> tag, but for modules the code could be added to the
> main module .js file.
> I’m not sure about this. I think typically you inject a <link
> href=”x”> for css and a <script src=”y”> for the js. How do you propose to
> add those to the module js?
>
> On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Hi Carlos, thanks. The issue is with inject_html in modules on IE,
> dialogPolyfill.js just happened to be the target src here. I’ve been
> searching the net for solutions on IE and I think the trick is to append
> elements instead of changing the inner html. I see two options of
> transpiling <inject_html> that would work on IE:
>
>
> 1. Parse the <inject_html> contents in the compiler and create
> js that would work for IE. Difficult.
> 2. Replace each line in <inject_html> with dummy elements and
> change their outerHTML to match each line contents. This one looks easier,
> but I seem to remember a thread where we were trying to eliminate use of
> outerHTML.
>
>
> Any thoughts are welcome.
>
> From: Carlos Rovira<ma...@apache.org>
> Sent: Monday, May 11, 2020 6:06 PM
> To: Apache Royale Development<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Hi Yishay,
>
> talking without a huge analisys of the problem. I think Jewel
> Alert works
> ok in IE11 so that should mean dialogpolyfil is loading ok. if not
> the case
> something broke recently since I checked that in TDJ and other
> apps we did.
>
> Anyway, the commit you state is just to give the support we
> needed. I
> didn't tested in IE11, so don't know if we support it. Normally
> IE11 use to
> require
> some special way of writing the code for some particular things,
> so I think
> the way to solve this is:
>
> 1.- search in SOF or other sources how IE11 expect scripts to be
> added
> dynamically
> 2.- upgrade the compiler code to use that way with that
> considerations to
> make it IE11 compatible and check if that works for IE11 and rest
> of
> browsers.
>
> sorry to not be able to say much more, but I'm these days with few
> time
>
> Thanks
>
>
>
> El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<
> yishayjobs@hotmail.com>)
> escribió:
>
> > Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in
> compiler code
> > doesn’t work for IE11. Any ideas on how to fix this?
> >
> > From: Yishay Weiss<ma...@hotmail.com>
> > Sent: Monday, May 11, 2020 4:52 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > These lines in dialogPolyfill.as
> >
> > * <inject_html>
> > * <script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324237150&sdata=mXiJMCztzMYBH6D6LM0%2Bdv2m4gFmFAoqpC%2FTVmjbn8g%3D&reserved=0
> > "></script>
> >
> > get transpiled to
> >
> > document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324237150&sdata=mXiJMCztzMYBH6D6LM0%2Bdv2m4gFmFAoqpC%2FTVmjbn8g%3D&reserved=0
> > "></script>'
> >
> > But that’s making IE11 fail in loading the module. It doesn’t
> matter what
> > the src is, IE will silently fail. For example, I’m getting the
> same result
> > if I replace the above with
> >
> > document.head.innerHTML += '<script></script>'
> >
> >
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 7:35:55 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Does dialog-polyfill load correctly? Does it muck with the
> window object?
> >
> > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > Test1.js isn’t different, but Test1_deps.js is.
> >
> > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > index 73eccbe..3e1a8a7 100644
> > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > @@ -211,4 +211,4 @@
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > ['org
> > goog.addDependency('../../../XML.js', ['XML'], []);
> >
> > goog.require('Test1');
> > -document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324237150&sdata=mXiJMCztzMYBH6D6LM0%2Bdv2m4gFmFAoqpC%2FTVmjbn8g%3D&reserved=0
> > "></script<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324237150&sdata=mXiJMCztzMYBH6D6LM0%2Bdv2m4gFmFAoqpC%2FTVmjbn8g%3D&reserved=0
> > >>';document.head.innerHTM
> > L += '<link rel="stylesheet" type="text/css" href="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=AiwgqYg2zTmgRs%2BzC3B82UOeIyedm9L6%2BS6%2FzkGKL0A%3D&reserved=0
> > ">';
> > +
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 6:39 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Interesting. Just adding import shouldn't affect the
> output. What is
> > the difference between Test1.js with and without that import
> statement?
> >
> > -Alex
> >
> > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > I’ve narrowed it down to usage of mx.controls.Alert.
> Test case is
> > included in this issue [1].
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=5XnYhvhgfJsonuIf0fHF%2FSSEDbgiow1Tbh345oQ7aC0%3D&reserved=0
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Thursday, May 7, 2020 10:35 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I think you can verify by debugging in some other
> browser and see
> > if breakpoints get set.
> >
> > A common “bug” in Flex modules was to reference and link
> the
> > module class into the loading app. I have no idea what will
> happen if you
> > have such a situation in Royale. You can look at the loading
> app’s
> > link-report to see if the module (Test1) is linked in the app
> and probably
> > see if Test1.js is in the output of the app if you start clean
> and do not
> > compile the module.
> >
> > HTH,
> > -Alex
> >
> > From: Yishay Weiss <yi...@hotmail.com>
> > Reply-To: "dev@royale.apache.org" <dev@royale.apache.org
> >
> > Date: Thursday, May 7, 2020 at 12:26 PM
> > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > url is
> >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>>>>>>
> >
> > I don’t see errors other than
> >
> > SEC7113: CSS was ignored due to mime type mismatch
> >
> > But I don’t think that’s it.
> >
> > I put a debugger; statement on the first line of the src
> which
> > never kicks.
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any
> errors
> > loading and running it? Are the other Royale packages/classes
> in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something
> else
> > creates a "window" property at the global window causing our
> package lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com> wrote:
> >
> > In my example <script> element is there but it’s
> never loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and
> it worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of
> <script> tags in
> > the head. Near the end of the list should be the script for the
> .js file
> > for the module.
> > Do you see any exceptions? ModuleExample works
> without errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58 PM
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any
> errors
> > loading and running it? Are the other Royale packages/classes
> in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something
> else
> > creates a "window" property at the global window causing our
> package lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com> wrote:
> >
> > In my example <script> element is there but it’s
> never loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and
> it worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of
> <script> tags in
> > the head. Near the end of the list should be the script for the
> .js file
> > for the module.
> > Do you see any exceptions? ModuleExample works
> without errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 7:36 PM
> > Subject: Re: Modules in IE
> >
> > Does dialog-polyfill load correctly? Does it muck with the
> window object?
> >
> > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > Test1.js isn’t different, but Test1_deps.js is.
> >
> > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > index 73eccbe..3e1a8a7 100644
> > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > @@ -211,4 +211,4 @@
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > ['org
> > goog.addDependency('../../../XML.js', ['XML'], []);
> >
> > goog.require('Test1');
> > -document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=B8KlNfzVS6I6U8V%2Bj6EOYDSjsxWPpuhGJ98XYfi%2ByEM%3D&reserved=0
> > "></script<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=B8KlNfzVS6I6U8V%2Bj6EOYDSjsxWPpuhGJ98XYfi%2ByEM%3D&reserved=0
> > >>';document.head.innerHTM
> > L += '<link rel="stylesheet" type="text/css" href="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=AiwgqYg2zTmgRs%2BzC3B82UOeIyedm9L6%2BS6%2FzkGKL0A%3D&reserved=0
> > ">';
> > +
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 6:39 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Interesting. Just adding import shouldn't affect the
> output. What is
> > the difference between Test1.js with and without that import
> statement?
> >
> > -Alex
> >
> > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > I’ve narrowed it down to usage of mx.controls.Alert.
> Test case is
> > included in this issue [1].
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=5XnYhvhgfJsonuIf0fHF%2FSSEDbgiow1Tbh345oQ7aC0%3D&reserved=0
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Thursday, May 7, 2020 10:35 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I think you can verify by debugging in some other
> browser and see
> > if breakpoints get set.
> >
> > A common “bug” in Flex modules was to reference and link
> the
> > module class into the loading app. I have no idea what will
> happen if you
> > have such a situation in Royale. You can look at the loading
> app’s
> > link-report to see if the module (Test1) is linked in the app
> and probably
> > see if Test1.js is in the output of the app if you start clean
> and do not
> > compile the module.
> >
> > HTH,
> > -Alex
> >
> > From: Yishay Weiss <yi...@hotmail.com>
> > Reply-To: "dev@royale.apache.org" <dev@royale.apache.org
> >
> > Date: Thursday, May 7, 2020 at 12:26 PM
> > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > url is
> >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>>>>>>
> >
> > I don’t see errors other than
> >
> > SEC7113: CSS was ignored due to mime type mismatch
> >
> > But I don’t think that’s it.
> >
> > I put a debugger; statement on the first line of the src
> which
> > never kicks.
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any
> errors
> > loading and running it? Are the other Royale packages/classes
> in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something
> else
> > creates a "window" property at the global window causing our
> package lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com> wrote:
> >
> > In my example <script> element is there but it’s
> never loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and
> it worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of
> <script> tags in
> > the head. Near the end of the list should be the script for the
> .js file
> > for the module.
> > Do you see any exceptions? ModuleExample works
> without errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58 PM
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any
> errors
> > loading and running it? Are the other Royale packages/classes
> in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something
> else
> > creates a "window" property at the global window causing our
> package lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com> wrote:
> >
> > In my example <script> element is there but it’s
> never loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and
> it worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of
> <script> tags in
> > the head. Near the end of the list should be the script for the
> .js file
> > for the module.
> > Do you see any exceptions? ModuleExample works
> without errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=oEuPO1QRYw31eRbzyd%2Bzqf1zHAH%2FUBX5B41zvuq8ZQs%3D&reserved=0
>
>
>
>
>
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
RE: Modules in IE
Posted by Yishay Weiss <yi...@hotmail.com>.
I’ve implemented this idea in inject_script branches for compiler and as-js. If someone has time test those it would be very helpful. It works for my case. I’ll do some more basic testing and if there are no objections I’ll merge tomorrow. Thanks.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Monday, May 11, 2020 8:05 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
My idea wasn't quite that. It was to write the injection in JS instead of HTML. Here's a current inject_html from dialogPolyfill.as
/**
* <inject_html>
* <script src="https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js"></script<https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js%22%3e%3c/script>>
* <link rel="stylesheet" type="text/css" href="https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.css">
* </inject_html>
*/
I think if it was rewritten as:
/**
* <inject_script>
* var script = document.createElement("script");
* script.setAttribute("src", "https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js");
* document.head.appendChild(script)
* var link = document.createElement("link");
* link.setAttribute("rel", "stylesheet");
* link.setAttribute("type", "text/css");
* link.setAttribute("href", "https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.css");
* document.head.appendChild(link);
* </inject_script>
*/
Then all the compiler needs to do is copy that JS into the appropriate file. I suppose we could always prepend it to the .js file, but I think if we wanted we could inject it into the html wrapper by copying the entire contents in between <script></script> tags.
The compiler would not have to parse anything, just copy like it currently does. We would have to go and re-write all of the current inject_htmls, although, as I said earlier, I think many inject_htmls should be replaced by other mechanism like static initializers. The real need for inject_html/inject_script is to make sure some external dependency has been loaded so a class can initialize (as the various clss.prototype.foo get interpreted). If the class just needs the dependency at runtime, load it later in the code for the class. That makes it more PAYG as well.
Of course, I could be wrong...
-Alex
On 5/11/20, 9:18 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
I guess I could add
<inject_script src=””/> and <inject_link href=””/> syntax which would be easier to parse and then transpile that, similar to how it’s done today. Before I go too crazy though, can someone remind me why outerHTML is evil?
Thanks.
From: Yishay Weiss<ma...@hotmail.com>
Sent: Monday, May 11, 2020 7:00 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: RE: Modules in IE
>What if we abandon "inject_html" and go with "inject_script" instead? Then when adding to the html output, each >script would be wrapped with a <script> tag, but for modules the code could be added to the main module .js file.
I’m not sure about this. I think typically you inject a <link href=”x”> for css and a <script src=”y”> for the js. How do you propose to add those to the module js?
On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
Hi Carlos, thanks. The issue is with inject_html in modules on IE, dialogPolyfill.js just happened to be the target src here. I’ve been searching the net for solutions on IE and I think the trick is to append elements instead of changing the inner html. I see two options of transpiling <inject_html> that would work on IE:
1. Parse the <inject_html> contents in the compiler and create js that would work for IE. Difficult.
2. Replace each line in <inject_html> with dummy elements and change their outerHTML to match each line contents. This one looks easier, but I seem to remember a thread where we were trying to eliminate use of outerHTML.
Any thoughts are welcome.
From: Carlos Rovira<ma...@apache.org>
Sent: Monday, May 11, 2020 6:06 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: Modules in IE
Hi Yishay,
talking without a huge analisys of the problem. I think Jewel Alert works
ok in IE11 so that should mean dialogpolyfil is loading ok. if not the case
something broke recently since I checked that in TDJ and other apps we did.
Anyway, the commit you state is just to give the support we needed. I
didn't tested in IE11, so don't know if we support it. Normally IE11 use to
require
some special way of writing the code for some particular things, so I think
the way to solve this is:
1.- search in SOF or other sources how IE11 expect scripts to be added
dynamically
2.- upgrade the compiler code to use that way with that considerations to
make it IE11 compatible and check if that works for IE11 and rest of
browsers.
sorry to not be able to say much more, but I'm these days with few time
Thanks
El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<yi...@hotmail.com>)
escribió:
> Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in compiler code
> doesn’t work for IE11. Any ideas on how to fix this?
>
> From: Yishay Weiss<ma...@hotmail.com>
> Sent: Monday, May 11, 2020 4:52 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: RE: Modules in IE
>
> These lines in dialogPolyfill.as
>
> * <inject_html>
> * <script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324237150&sdata=mXiJMCztzMYBH6D6LM0%2Bdv2m4gFmFAoqpC%2FTVmjbn8g%3D&reserved=0
> "></script>
>
> get transpiled to
>
> document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324237150&sdata=mXiJMCztzMYBH6D6LM0%2Bdv2m4gFmFAoqpC%2FTVmjbn8g%3D&reserved=0
> "></script>'
>
> But that’s making IE11 fail in loading the module. It doesn’t matter what
> the src is, IE will silently fail. For example, I’m getting the same result
> if I replace the above with
>
> document.head.innerHTML += '<script></script>'
>
>
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:35:55 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324237150&sdata=mXiJMCztzMYBH6D6LM0%2Bdv2m4gFmFAoqpC%2FTVmjbn8g%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324237150&sdata=mXiJMCztzMYBH6D6LM0%2Bdv2m4gFmFAoqpC%2FTVmjbn8g%3D&reserved=0
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=AiwgqYg2zTmgRs%2BzC3B82UOeIyedm9L6%2BS6%2FzkGKL0A%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=5XnYhvhgfJsonuIf0fHF%2FSSEDbgiow1Tbh345oQ7aC0%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>>>>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:36 PM
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=B8KlNfzVS6I6U8V%2Bj6EOYDSjsxWPpuhGJ98XYfi%2ByEM%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=B8KlNfzVS6I6U8V%2Bj6EOYDSjsxWPpuhGJ98XYfi%2ByEM%3D&reserved=0
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=AiwgqYg2zTmgRs%2BzC3B82UOeIyedm9L6%2BS6%2FzkGKL0A%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=5XnYhvhgfJsonuIf0fHF%2FSSEDbgiow1Tbh345oQ7aC0%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>>>>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
Carlos Rovira
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=oEuPO1QRYw31eRbzyd%2Bzqf1zHAH%2FUBX5B41zvuq8ZQs%3D&reserved=0
Re: Modules in IE
Posted by Alex Harui <ah...@adobe.com.INVALID>.
My idea wasn't quite that. It was to write the injection in JS instead of HTML. Here's a current inject_html from dialogPolyfill.as
/**
* <inject_html>
* <script src="https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js"></script>
* <link rel="stylesheet" type="text/css" href="https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.css">
* </inject_html>
*/
I think if it was rewritten as:
/**
* <inject_script>
* var script = document.createElement("script");
* script.setAttribute("src", "https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js");
* document.head.appendChild(script)
* var link = document.createElement("link");
* link.setAttribute("rel", "stylesheet");
* link.setAttribute("type", "text/css");
* link.setAttribute("href", "https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.css");
* document.head.appendChild(link);
* </inject_script>
*/
Then all the compiler needs to do is copy that JS into the appropriate file. I suppose we could always prepend it to the .js file, but I think if we wanted we could inject it into the html wrapper by copying the entire contents in between <script></script> tags.
The compiler would not have to parse anything, just copy like it currently does. We would have to go and re-write all of the current inject_htmls, although, as I said earlier, I think many inject_htmls should be replaced by other mechanism like static initializers. The real need for inject_html/inject_script is to make sure some external dependency has been loaded so a class can initialize (as the various clss.prototype.foo get interpreted). If the class just needs the dependency at runtime, load it later in the code for the class. That makes it more PAYG as well.
Of course, I could be wrong...
-Alex
On 5/11/20, 9:18 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
I guess I could add
<inject_script src=””/> and <inject_link href=””/> syntax which would be easier to parse and then transpile that, similar to how it’s done today. Before I go too crazy though, can someone remind me why outerHTML is evil?
Thanks.
From: Yishay Weiss<ma...@hotmail.com>
Sent: Monday, May 11, 2020 7:00 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: RE: Modules in IE
>What if we abandon "inject_html" and go with "inject_script" instead? Then when adding to the html output, each >script would be wrapped with a <script> tag, but for modules the code could be added to the main module .js file.
I’m not sure about this. I think typically you inject a <link href=”x”> for css and a <script src=”y”> for the js. How do you propose to add those to the module js?
On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
Hi Carlos, thanks. The issue is with inject_html in modules on IE, dialogPolyfill.js just happened to be the target src here. I’ve been searching the net for solutions on IE and I think the trick is to append elements instead of changing the inner html. I see two options of transpiling <inject_html> that would work on IE:
1. Parse the <inject_html> contents in the compiler and create js that would work for IE. Difficult.
2. Replace each line in <inject_html> with dummy elements and change their outerHTML to match each line contents. This one looks easier, but I seem to remember a thread where we were trying to eliminate use of outerHTML.
Any thoughts are welcome.
From: Carlos Rovira<ma...@apache.org>
Sent: Monday, May 11, 2020 6:06 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: Modules in IE
Hi Yishay,
talking without a huge analisys of the problem. I think Jewel Alert works
ok in IE11 so that should mean dialogpolyfil is loading ok. if not the case
something broke recently since I checked that in TDJ and other apps we did.
Anyway, the commit you state is just to give the support we needed. I
didn't tested in IE11, so don't know if we support it. Normally IE11 use to
require
some special way of writing the code for some particular things, so I think
the way to solve this is:
1.- search in SOF or other sources how IE11 expect scripts to be added
dynamically
2.- upgrade the compiler code to use that way with that considerations to
make it IE11 compatible and check if that works for IE11 and rest of
browsers.
sorry to not be able to say much more, but I'm these days with few time
Thanks
El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<yi...@hotmail.com>)
escribió:
> Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in compiler code
> doesn’t work for IE11. Any ideas on how to fix this?
>
> From: Yishay Weiss<ma...@hotmail.com>
> Sent: Monday, May 11, 2020 4:52 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: RE: Modules in IE
>
> These lines in dialogPolyfill.as
>
> * <inject_html>
> * <script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324237150&sdata=mXiJMCztzMYBH6D6LM0%2Bdv2m4gFmFAoqpC%2FTVmjbn8g%3D&reserved=0
> "></script>
>
> get transpiled to
>
> document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324237150&sdata=mXiJMCztzMYBH6D6LM0%2Bdv2m4gFmFAoqpC%2FTVmjbn8g%3D&reserved=0
> "></script>'
>
> But that’s making IE11 fail in loading the module. It doesn’t matter what
> the src is, IE will silently fail. For example, I’m getting the same result
> if I replace the above with
>
> document.head.innerHTML += '<script></script>'
>
>
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:35:55 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324237150&sdata=mXiJMCztzMYBH6D6LM0%2Bdv2m4gFmFAoqpC%2FTVmjbn8g%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324237150&sdata=mXiJMCztzMYBH6D6LM0%2Bdv2m4gFmFAoqpC%2FTVmjbn8g%3D&reserved=0
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=AiwgqYg2zTmgRs%2BzC3B82UOeIyedm9L6%2BS6%2FzkGKL0A%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=5XnYhvhgfJsonuIf0fHF%2FSSEDbgiow1Tbh345oQ7aC0%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:36 PM
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=B8KlNfzVS6I6U8V%2Bj6EOYDSjsxWPpuhGJ98XYfi%2ByEM%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=B8KlNfzVS6I6U8V%2Bj6EOYDSjsxWPpuhGJ98XYfi%2ByEM%3D&reserved=0
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=AiwgqYg2zTmgRs%2BzC3B82UOeIyedm9L6%2BS6%2FzkGKL0A%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=5XnYhvhgfJsonuIf0fHF%2FSSEDbgiow1Tbh345oQ7aC0%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
Carlos Rovira
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C1a29cea822264af04d9e08d7f5c6fd7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248107324247118&sdata=oEuPO1QRYw31eRbzyd%2Bzqf1zHAH%2FUBX5B41zvuq8ZQs%3D&reserved=0
Re: Modules in IE
Posted by Carlos Rovira <ca...@apache.org>.
Hi,
I think Jewel Alert could implement Alex's suggestion by using "loadScript"
when necessary.
If other want to try that option would be good. If not I'll try at some
point, although I have many things in my plate for now.
Anyway, trying some workaround that solved the IE problem is something
worth it to do even optimizing things like Alert with loadScript.
Thanks
El mié., 13 may. 2020 a las 10:47, Carlos Rovira (<ca...@apache.org>)
escribió:
> Hi Yishay,
>
> catching here after some days. I think the issue with outerHTML is
> security as with innerHTML.
>
>
> http://blog.blueclosure.com/2017/09/javascript-dangerous-functions-part-1.html
>
>
> El lun., 11 may. 2020 a las 18:18, Yishay Weiss (<yi...@hotmail.com>)
> escribió:
>
>> I guess I could add
>>
>> <inject_script src=””/> and <inject_link href=””/> syntax which would be
>> easier to parse and then transpile that, similar to how it’s done today.
>> Before I go too crazy though, can someone remind me why outerHTML is evil?
>>
>> Thanks.
>>
>> From: Yishay Weiss<ma...@hotmail.com>
>> Sent: Monday, May 11, 2020 7:00 PM
>> To: dev@royale.apache.org<ma...@royale.apache.org>
>> Subject: RE: Modules in IE
>>
>>
>> >What if we abandon "inject_html" and go with "inject_script" instead?
>> Then when adding to the html output, each >script would be wrapped with a
>> <script> tag, but for modules the code could be added to the main module
>> .js file.
>> I’m not sure about this. I think typically you inject a <link href=”x”>
>> for css and a <script src=”y”> for the js. How do you propose to add those
>> to the module js?
>>
>> On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>>
>> Hi Carlos, thanks. The issue is with inject_html in modules on IE,
>> dialogPolyfill.js just happened to be the target src here. I’ve been
>> searching the net for solutions on IE and I think the trick is to append
>> elements instead of changing the inner html. I see two options of
>> transpiling <inject_html> that would work on IE:
>>
>>
>> 1. Parse the <inject_html> contents in the compiler and create js
>> that would work for IE. Difficult.
>> 2. Replace each line in <inject_html> with dummy elements and
>> change their outerHTML to match each line contents. This one looks easier,
>> but I seem to remember a thread where we were trying to eliminate use of
>> outerHTML.
>>
>>
>> Any thoughts are welcome.
>>
>> From: Carlos Rovira<ma...@apache.org>
>> Sent: Monday, May 11, 2020 6:06 PM
>> To: Apache Royale Development<ma...@royale.apache.org>
>> Subject: Re: Modules in IE
>>
>> Hi Yishay,
>>
>> talking without a huge analisys of the problem. I think Jewel Alert
>> works
>> ok in IE11 so that should mean dialogpolyfil is loading ok. if not
>> the case
>> something broke recently since I checked that in TDJ and other apps
>> we did.
>>
>> Anyway, the commit you state is just to give the support we needed. I
>> didn't tested in IE11, so don't know if we support it. Normally IE11
>> use to
>> require
>> some special way of writing the code for some particular things, so I
>> think
>> the way to solve this is:
>>
>> 1.- search in SOF or other sources how IE11 expect scripts to be added
>> dynamically
>> 2.- upgrade the compiler code to use that way with that
>> considerations to
>> make it IE11 compatible and check if that works for IE11 and rest of
>> browsers.
>>
>> sorry to not be able to say much more, but I'm these days with few
>> time
>>
>> Thanks
>>
>>
>>
>> El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<
>> yishayjobs@hotmail.com>)
>> escribió:
>>
>> > Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in
>> compiler code
>> > doesn’t work for IE11. Any ideas on how to fix this?
>> >
>> > From: Yishay Weiss<ma...@hotmail.com>
>> > Sent: Monday, May 11, 2020 4:52 PM
>> > To: dev@royale.apache.org<ma...@royale.apache.org>
>> > Subject: RE: Modules in IE
>> >
>> > These lines in dialogPolyfill.as
>> >
>> > * <inject_html>
>> > * <script src="
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
>> > "></script>
>> >
>> > get transpiled to
>> >
>> > document.head.innerHTML += '<script src="
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
>> > "></script>'
>> >
>> > But that’s making IE11 fail in loading the module. It doesn’t
>> matter what
>> > the src is, IE will silently fail. For example, I’m getting the
>> same result
>> > if I replace the above with
>> >
>> > document.head.innerHTML += '<script></script>'
>> >
>> >
>> >
>> >
>> > From: Alex Harui <ah...@adobe.com.INVALID>
>> > Sent: Sunday, May 10, 2020 7:35:55 PM
>> > To: dev@royale.apache.org <de...@royale.apache.org>
>> > Subject: Re: Modules in IE
>> >
>> > Does dialog-polyfill load correctly? Does it muck with the window
>> object?
>> >
>> > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>> >
>> > Test1.js isn’t different, but Test1_deps.js is.
>> >
>> > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
>> > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
>> > index 73eccbe..3e1a8a7 100644
>> > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
>> > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
>> > @@ -211,4 +211,4 @@
>> >
>> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
>> > ['org
>> > goog.addDependency('../../../XML.js', ['XML'], []);
>> >
>> > goog.require('Test1');
>> > -document.head.innerHTML += '<script src="
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
>> > "></script<
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
>> > >>';document.head.innerHTM
>> > L += '<link rel="stylesheet" type="text/css" href="
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=UhWgHnDOQVBBCGVW9RI3gwCcxHZcBcYjNu9bfmNEqbI%3D&reserved=0
>> > ">';
>> > +
>> >
>> > From: Alex Harui<ma...@adobe.com.INVALID>
>> > Sent: Sunday, May 10, 2020 6:39 PM
>> > To: dev@royale.apache.org<ma...@royale.apache.org>
>> > Subject: Re: Modules in IE
>> >
>> > Interesting. Just adding import shouldn't affect the output.
>> What is
>> > the difference between Test1.js with and without that import
>> statement?
>> >
>> > -Alex
>> >
>> > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
>> wrote:
>> >
>> > I’ve narrowed it down to usage of mx.controls.Alert. Test
>> case is
>> > included in this issue [1].
>> >
>> > [1]
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=k5fxV4D7kTCIKILQxTYLYkIlTG29sSNaJiJ0gdnXkXM%3D&reserved=0
>> >
>> > From: Alex Harui<ma...@adobe.com.INVALID>
>> > Sent: Thursday, May 7, 2020 10:35 PM
>> > To: dev@royale.apache.org<ma...@royale.apache.org>
>> > Subject: Re: Modules in IE
>> >
>> > I think you can verify by debugging in some other browser
>> and see
>> > if breakpoints get set.
>> >
>> > A common “bug” in Flex modules was to reference and link the
>> > module class into the loading app. I have no idea what will happen
>> if you
>> > have such a situation in Royale. You can look at the loading app’s
>> > link-report to see if the module (Test1) is linked in the app and
>> probably
>> > see if Test1.js is in the output of the app if you start clean and
>> do not
>> > compile the module.
>> >
>> > HTH,
>> > -Alex
>> >
>> > From: Yishay Weiss <yi...@hotmail.com>
>> > Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
>> > Date: Thursday, May 7, 2020 at 12:26 PM
>> > To: "dev@royale.apache.org" <de...@royale.apache.org>
>> > Subject: RE: Modules in IE
>> >
>> > url is
>> >
>> >
>> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>>
>> >
>> > I don’t see errors other than
>> >
>> > SEC7113: CSS was ignored due to mime type mismatch
>> >
>> > But I don’t think that’s it.
>> >
>> > I put a debugger; statement on the first line of the src
>> which
>> > never kicks.
>> >
>> >
>> > From: Alex Harui <ah...@adobe.com.INVALID>
>> > Sent: Wednesday, May 6, 2020 7:58:15 PM
>> > To: dev@royale.apache.org <de...@royale.apache.org>
>> > Subject: Re: Modules in IE
>> >
>> > What is the src (url) for that script? Were there any
>> errors
>> > loading and running it? Are the other Royale packages/classes in
>> the
>> > "window" object?
>> >
>> > One scenario I thought of is that some bug or something else
>> > creates a "window" property at the global window causing our
>> package lookup
>> > to be off.
>> >
>> > HTH,
>> > -Alex
>> >
>> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
>> wrote:
>> >
>> > In my example <script> element is there but it’s never
>> loaded
>> > on IE. I can confirm ModuleExamle works.
>> >
>> > From: Alex Harui<ma...@adobe.com.INVALID>
>> > Sent: Sunday, May 3, 2020 9:31 AM
>> > To: dev@royale.apache.org<ma...@royale.apache.org>
>> > Subject: Re: Modules in IE
>> >
>> > I just ran examples/royale/ModuleExample in IE and it
>> worked.
>> > Does it work for you?
>> > In the debugger, window.Module and window.MainApp
>> resolve to
>> > functions. window.org is an object with an apache property.
>> > In the DOM Explorer, there should be tons of <script>
>> tags in
>> > the head. Near the end of the list should be the script for the
>> .js file
>> > for the module.
>> > Do you see any exceptions? ModuleExample works without
>> errors.
>> >
>> > -Alex
>> >
>> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
>> yishayjobs@hotmail.com>
>> > wrote:
>> >
>> > 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<ma...@adobe.com.INVALID>
>> > Sent: Thursday, April 30, 2020 6:29 AM
>> > To: dev@royale.apache.org<mailto:
>> dev@royale.apache.org>
>> > 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" <
>> > yishayjobs@hotmail.com> 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:
>> aharui@adobe.com.INVALID>
>> > Sent: Thursday, April 30, 2020 12:00 AM
>> > To: dev@royale.apache.org<mailto:
>> dev@royale.apache.org
>> > >
>> > 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" <
>> > yishayjobs@hotmail.com> 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.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > From: Alex Harui<ma...@adobe.com.INVALID>
>> > Sent: Wednesday, May 6, 2020 7:58 PM
>> > Subject: Re: Modules in IE
>> >
>> > What is the src (url) for that script? Were there any
>> errors
>> > loading and running it? Are the other Royale packages/classes in
>> the
>> > "window" object?
>> >
>> > One scenario I thought of is that some bug or something else
>> > creates a "window" property at the global window causing our
>> package lookup
>> > to be off.
>> >
>> > HTH,
>> > -Alex
>> >
>> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
>> wrote:
>> >
>> > In my example <script> element is there but it’s never
>> loaded
>> > on IE. I can confirm ModuleExamle works.
>> >
>> > From: Alex Harui<ma...@adobe.com.INVALID>
>> > Sent: Sunday, May 3, 2020 9:31 AM
>> > To: dev@royale.apache.org<ma...@royale.apache.org>
>> > Subject: Re: Modules in IE
>> >
>> > I just ran examples/royale/ModuleExample in IE and it
>> worked.
>> > Does it work for you?
>> > In the debugger, window.Module and window.MainApp
>> resolve to
>> > functions. window.org is an object with an apache property.
>> > In the DOM Explorer, there should be tons of <script>
>> tags in
>> > the head. Near the end of the list should be the script for the
>> .js file
>> > for the module.
>> > Do you see any exceptions? ModuleExample works without
>> errors.
>> >
>> > -Alex
>> >
>> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
>> yishayjobs@hotmail.com>
>> > wrote:
>> >
>> > 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<ma...@adobe.com.INVALID>
>> > Sent: Thursday, April 30, 2020 6:29 AM
>> > To: dev@royale.apache.org<mailto:
>> dev@royale.apache.org>
>> > 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" <
>> > yishayjobs@hotmail.com> 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:
>> aharui@adobe.com.INVALID>
>> > Sent: Thursday, April 30, 2020 12:00 AM
>> > To: dev@royale.apache.org<mailto:
>> dev@royale.apache.org
>> > >
>> > 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" <
>> > yishayjobs@hotmail.com> 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.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > From: Alex Harui<ma...@adobe.com.INVALID>
>> > Sent: Sunday, May 10, 2020 7:36 PM
>> > Subject: Re: Modules in IE
>> >
>> > Does dialog-polyfill load correctly? Does it muck with the window
>> object?
>> >
>> > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>> >
>> > Test1.js isn’t different, but Test1_deps.js is.
>> >
>> > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
>> > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
>> > index 73eccbe..3e1a8a7 100644
>> > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
>> > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
>> > @@ -211,4 +211,4 @@
>> >
>> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
>> > ['org
>> > goog.addDependency('../../../XML.js', ['XML'], []);
>> >
>> > goog.require('Test1');
>> > -document.head.innerHTML += '<script src="
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
>> > "></script<
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
>> > >>';document.head.innerHTM
>> > L += '<link rel="stylesheet" type="text/css" href="
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=90IzQjbCvQTqLKnJv4B0q0xP8L7tKRBcGZkeLzsv1hU%3D&reserved=0
>> > ">';
>> > +
>> >
>> > From: Alex Harui<ma...@adobe.com.INVALID>
>> > Sent: Sunday, May 10, 2020 6:39 PM
>> > To: dev@royale.apache.org<ma...@royale.apache.org>
>> > Subject: Re: Modules in IE
>> >
>> > Interesting. Just adding import shouldn't affect the output.
>> What is
>> > the difference between Test1.js with and without that import
>> statement?
>> >
>> > -Alex
>> >
>> > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
>> wrote:
>> >
>> > I’ve narrowed it down to usage of mx.controls.Alert. Test
>> case is
>> > included in this issue [1].
>> >
>> > [1]
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=evkgF0%2BsdYs2Irz1Jigsgmn6Yq4IS7e4LLvGCJ4EReY%3D&reserved=0
>> >
>> > From: Alex Harui<ma...@adobe.com.INVALID>
>> > Sent: Thursday, May 7, 2020 10:35 PM
>> > To: dev@royale.apache.org<ma...@royale.apache.org>
>> > Subject: Re: Modules in IE
>> >
>> > I think you can verify by debugging in some other browser
>> and see
>> > if breakpoints get set.
>> >
>> > A common “bug” in Flex modules was to reference and link the
>> > module class into the loading app. I have no idea what will happen
>> if you
>> > have such a situation in Royale. You can look at the loading app’s
>> > link-report to see if the module (Test1) is linked in the app and
>> probably
>> > see if Test1.js is in the output of the app if you start clean and
>> do not
>> > compile the module.
>> >
>> > HTH,
>> > -Alex
>> >
>> > From: Yishay Weiss <yi...@hotmail.com>
>> > Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
>> > Date: Thursday, May 7, 2020 at 12:26 PM
>> > To: "dev@royale.apache.org" <de...@royale.apache.org>
>> > Subject: RE: Modules in IE
>> >
>> > url is
>> >
>> >
>> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>>
>> >
>> > I don’t see errors other than
>> >
>> > SEC7113: CSS was ignored due to mime type mismatch
>> >
>> > But I don’t think that’s it.
>> >
>> > I put a debugger; statement on the first line of the src
>> which
>> > never kicks.
>> >
>> >
>> > From: Alex Harui <ah...@adobe.com.INVALID>
>> > Sent: Wednesday, May 6, 2020 7:58:15 PM
>> > To: dev@royale.apache.org <de...@royale.apache.org>
>> > Subject: Re: Modules in IE
>> >
>> > What is the src (url) for that script? Were there any
>> errors
>> > loading and running it? Are the other Royale packages/classes in
>> the
>> > "window" object?
>> >
>> > One scenario I thought of is that some bug or something else
>> > creates a "window" property at the global window causing our
>> package lookup
>> > to be off.
>> >
>> > HTH,
>> > -Alex
>> >
>> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
>> wrote:
>> >
>> > In my example <script> element is there but it’s never
>> loaded
>> > on IE. I can confirm ModuleExamle works.
>> >
>> > From: Alex Harui<ma...@adobe.com.INVALID>
>> > Sent: Sunday, May 3, 2020 9:31 AM
>> > To: dev@royale.apache.org<ma...@royale.apache.org>
>> > Subject: Re: Modules in IE
>> >
>> > I just ran examples/royale/ModuleExample in IE and it
>> worked.
>> > Does it work for you?
>> > In the debugger, window.Module and window.MainApp
>> resolve to
>> > functions. window.org is an object with an apache property.
>> > In the DOM Explorer, there should be tons of <script>
>> tags in
>> > the head. Near the end of the list should be the script for the
>> .js file
>> > for the module.
>> > Do you see any exceptions? ModuleExample works without
>> errors.
>> >
>> > -Alex
>> >
>> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
>> yishayjobs@hotmail.com>
>> > wrote:
>> >
>> > 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<ma...@adobe.com.INVALID>
>> > Sent: Thursday, April 30, 2020 6:29 AM
>> > To: dev@royale.apache.org<mailto:
>> dev@royale.apache.org>
>> > 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" <
>> > yishayjobs@hotmail.com> 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:
>> aharui@adobe.com.INVALID>
>> > Sent: Thursday, April 30, 2020 12:00 AM
>> > To: dev@royale.apache.org<mailto:
>> dev@royale.apache.org
>> > >
>> > 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" <
>> > yishayjobs@hotmail.com> 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.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > From: Alex Harui<ma...@adobe.com.INVALID>
>> > Sent: Wednesday, May 6, 2020 7:58 PM
>> > Subject: Re: Modules in IE
>> >
>> > What is the src (url) for that script? Were there any
>> errors
>> > loading and running it? Are the other Royale packages/classes in
>> the
>> > "window" object?
>> >
>> > One scenario I thought of is that some bug or something else
>> > creates a "window" property at the global window causing our
>> package lookup
>> > to be off.
>> >
>> > HTH,
>> > -Alex
>> >
>> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
>> wrote:
>> >
>> > In my example <script> element is there but it’s never
>> loaded
>> > on IE. I can confirm ModuleExamle works.
>> >
>> > From: Alex Harui<ma...@adobe.com.INVALID>
>> > Sent: Sunday, May 3, 2020 9:31 AM
>> > To: dev@royale.apache.org<ma...@royale.apache.org>
>> > Subject: Re: Modules in IE
>> >
>> > I just ran examples/royale/ModuleExample in IE and it
>> worked.
>> > Does it work for you?
>> > In the debugger, window.Module and window.MainApp
>> resolve to
>> > functions. window.org is an object with an apache property.
>> > In the DOM Explorer, there should be tons of <script>
>> tags in
>> > the head. Near the end of the list should be the script for the
>> .js file
>> > for the module.
>> > Do you see any exceptions? ModuleExample works without
>> errors.
>> >
>> > -Alex
>> >
>> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
>> yishayjobs@hotmail.com>
>> > wrote:
>> >
>> > 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<ma...@adobe.com.INVALID>
>> > Sent: Thursday, April 30, 2020 6:29 AM
>> > To: dev@royale.apache.org<mailto:
>> dev@royale.apache.org>
>> > 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" <
>> > yishayjobs@hotmail.com> 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:
>> aharui@adobe.com.INVALID>
>> > Sent: Thursday, April 30, 2020 12:00 AM
>> > To: dev@royale.apache.org<mailto:
>> dev@royale.apache.org
>> > >
>> > 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" <
>> > yishayjobs@hotmail.com> 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.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>> --
>> Carlos Rovira
>>
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=L0ya5B62P40fyCYZolQxaDCkYF0cbmuDHZhURTCXLPw%3D&reserved=0
>>
>>
>>
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Modules in IE
Posted by Carlos Rovira <ca...@apache.org>.
Hi Yishay,
catching here after some days. I think the issue with outerHTML is security
as with innerHTML.
http://blog.blueclosure.com/2017/09/javascript-dangerous-functions-part-1.html
El lun., 11 may. 2020 a las 18:18, Yishay Weiss (<yi...@hotmail.com>)
escribió:
> I guess I could add
>
> <inject_script src=””/> and <inject_link href=””/> syntax which would be
> easier to parse and then transpile that, similar to how it’s done today.
> Before I go too crazy though, can someone remind me why outerHTML is evil?
>
> Thanks.
>
> From: Yishay Weiss<ma...@hotmail.com>
> Sent: Monday, May 11, 2020 7:00 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: RE: Modules in IE
>
>
> >What if we abandon "inject_html" and go with "inject_script" instead?
> Then when adding to the html output, each >script would be wrapped with a
> <script> tag, but for modules the code could be added to the main module
> .js file.
> I’m not sure about this. I think typically you inject a <link href=”x”>
> for css and a <script src=”y”> for the js. How do you propose to add those
> to the module js?
>
> On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Hi Carlos, thanks. The issue is with inject_html in modules on IE,
> dialogPolyfill.js just happened to be the target src here. I’ve been
> searching the net for solutions on IE and I think the trick is to append
> elements instead of changing the inner html. I see two options of
> transpiling <inject_html> that would work on IE:
>
>
> 1. Parse the <inject_html> contents in the compiler and create js
> that would work for IE. Difficult.
> 2. Replace each line in <inject_html> with dummy elements and
> change their outerHTML to match each line contents. This one looks easier,
> but I seem to remember a thread where we were trying to eliminate use of
> outerHTML.
>
>
> Any thoughts are welcome.
>
> From: Carlos Rovira<ma...@apache.org>
> Sent: Monday, May 11, 2020 6:06 PM
> To: Apache Royale Development<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Hi Yishay,
>
> talking without a huge analisys of the problem. I think Jewel Alert
> works
> ok in IE11 so that should mean dialogpolyfil is loading ok. if not the
> case
> something broke recently since I checked that in TDJ and other apps we
> did.
>
> Anyway, the commit you state is just to give the support we needed. I
> didn't tested in IE11, so don't know if we support it. Normally IE11
> use to
> require
> some special way of writing the code for some particular things, so I
> think
> the way to solve this is:
>
> 1.- search in SOF or other sources how IE11 expect scripts to be added
> dynamically
> 2.- upgrade the compiler code to use that way with that considerations
> to
> make it IE11 compatible and check if that works for IE11 and rest of
> browsers.
>
> sorry to not be able to say much more, but I'm these days with few time
>
> Thanks
>
>
>
> El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<
> yishayjobs@hotmail.com>)
> escribió:
>
> > Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in compiler
> code
> > doesn’t work for IE11. Any ideas on how to fix this?
> >
> > From: Yishay Weiss<ma...@hotmail.com>
> > Sent: Monday, May 11, 2020 4:52 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > These lines in dialogPolyfill.as
> >
> > * <inject_html>
> > * <script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > "></script>
> >
> > get transpiled to
> >
> > document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > "></script>'
> >
> > But that’s making IE11 fail in loading the module. It doesn’t matter
> what
> > the src is, IE will silently fail. For example, I’m getting the same
> result
> > if I replace the above with
> >
> > document.head.innerHTML += '<script></script>'
> >
> >
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 7:35:55 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Does dialog-polyfill load correctly? Does it muck with the window
> object?
> >
> > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> >
> > Test1.js isn’t different, but Test1_deps.js is.
> >
> > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > index 73eccbe..3e1a8a7 100644
> > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > @@ -211,4 +211,4 @@
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > ['org
> > goog.addDependency('../../../XML.js', ['XML'], []);
> >
> > goog.require('Test1');
> > -document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > "></script<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > >>';document.head.innerHTM
> > L += '<link rel="stylesheet" type="text/css" href="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=UhWgHnDOQVBBCGVW9RI3gwCcxHZcBcYjNu9bfmNEqbI%3D&reserved=0
> > ">';
> > +
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 6:39 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Interesting. Just adding import shouldn't affect the output.
> What is
> > the difference between Test1.js with and without that import
> statement?
> >
> > -Alex
> >
> > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > I’ve narrowed it down to usage of mx.controls.Alert. Test
> case is
> > included in this issue [1].
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=k5fxV4D7kTCIKILQxTYLYkIlTG29sSNaJiJ0gdnXkXM%3D&reserved=0
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Thursday, May 7, 2020 10:35 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I think you can verify by debugging in some other browser
> and see
> > if breakpoints get set.
> >
> > A common “bug” in Flex modules was to reference and link the
> > module class into the loading app. I have no idea what will happen
> if you
> > have such a situation in Royale. You can look at the loading app’s
> > link-report to see if the module (Test1) is linked in the app and
> probably
> > see if Test1.js is in the output of the app if you start clean and
> do not
> > compile the module.
> >
> > HTH,
> > -Alex
> >
> > From: Yishay Weiss <yi...@hotmail.com>
> > Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Date: Thursday, May 7, 2020 at 12:26 PM
> > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > url is
> >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>>
> >
> > I don’t see errors other than
> >
> > SEC7113: CSS was ignored due to mime type mismatch
> >
> > But I don’t think that’s it.
> >
> > I put a debugger; statement on the first line of the src
> which
> > never kicks.
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any errors
> > loading and running it? Are the other Royale packages/classes in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something else
> > creates a "window" property at the global window causing our package
> lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > In my example <script> element is there but it’s never
> loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and it
> worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of <script>
> tags in
> > the head. Near the end of the list should be the script for the .js
> file
> > for the module.
> > Do you see any exceptions? ModuleExample works without
> errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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<ma...@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58 PM
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any errors
> > loading and running it? Are the other Royale packages/classes in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something else
> > creates a "window" property at the global window causing our package
> lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > In my example <script> element is there but it’s never
> loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and it
> worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of <script>
> tags in
> > the head. Near the end of the list should be the script for the .js
> file
> > for the module.
> > Do you see any exceptions? ModuleExample works without
> errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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<ma...@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 7:36 PM
> > Subject: Re: Modules in IE
> >
> > Does dialog-polyfill load correctly? Does it muck with the window
> object?
> >
> > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> >
> > Test1.js isn’t different, but Test1_deps.js is.
> >
> > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > index 73eccbe..3e1a8a7 100644
> > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > @@ -211,4 +211,4 @@
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > ['org
> > goog.addDependency('../../../XML.js', ['XML'], []);
> >
> > goog.require('Test1');
> > -document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > "></script<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > >>';document.head.innerHTM
> > L += '<link rel="stylesheet" type="text/css" href="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=90IzQjbCvQTqLKnJv4B0q0xP8L7tKRBcGZkeLzsv1hU%3D&reserved=0
> > ">';
> > +
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 6:39 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Interesting. Just adding import shouldn't affect the output.
> What is
> > the difference between Test1.js with and without that import
> statement?
> >
> > -Alex
> >
> > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > I’ve narrowed it down to usage of mx.controls.Alert. Test
> case is
> > included in this issue [1].
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=evkgF0%2BsdYs2Irz1Jigsgmn6Yq4IS7e4LLvGCJ4EReY%3D&reserved=0
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Thursday, May 7, 2020 10:35 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I think you can verify by debugging in some other browser
> and see
> > if breakpoints get set.
> >
> > A common “bug” in Flex modules was to reference and link the
> > module class into the loading app. I have no idea what will happen
> if you
> > have such a situation in Royale. You can look at the loading app’s
> > link-report to see if the module (Test1) is linked in the app and
> probably
> > see if Test1.js is in the output of the app if you start clean and
> do not
> > compile the module.
> >
> > HTH,
> > -Alex
> >
> > From: Yishay Weiss <yi...@hotmail.com>
> > Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Date: Thursday, May 7, 2020 at 12:26 PM
> > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > url is
> >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>>
> >
> > I don’t see errors other than
> >
> > SEC7113: CSS was ignored due to mime type mismatch
> >
> > But I don’t think that’s it.
> >
> > I put a debugger; statement on the first line of the src
> which
> > never kicks.
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any errors
> > loading and running it? Are the other Royale packages/classes in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something else
> > creates a "window" property at the global window causing our package
> lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > In my example <script> element is there but it’s never
> loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and it
> worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of <script>
> tags in
> > the head. Near the end of the list should be the script for the .js
> file
> > for the module.
> > Do you see any exceptions? ModuleExample works without
> errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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<ma...@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58 PM
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any errors
> > loading and running it? Are the other Royale packages/classes in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something else
> > creates a "window" property at the global window causing our package
> lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > In my example <script> element is there but it’s never
> loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and it
> worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of <script>
> tags in
> > the head. Near the end of the list should be the script for the .js
> file
> > for the module.
> > Do you see any exceptions? ModuleExample works without
> errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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<ma...@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=L0ya5B62P40fyCYZolQxaDCkYF0cbmuDHZhURTCXLPw%3D&reserved=0
>
>
>
>
>
--
Carlos Rovira
http://about.me/carlosrovira
RE: Modules in IE
Posted by Yishay Weiss <yi...@hotmail.com>.
I guess I could add
<inject_script src=””/> and <inject_link href=””/> syntax which would be easier to parse and then transpile that, similar to how it’s done today. Before I go too crazy though, can someone remind me why outerHTML is evil?
Thanks.
From: Yishay Weiss<ma...@hotmail.com>
Sent: Monday, May 11, 2020 7:00 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: RE: Modules in IE
>What if we abandon "inject_html" and go with "inject_script" instead? Then when adding to the html output, each >script would be wrapped with a <script> tag, but for modules the code could be added to the main module .js file.
I’m not sure about this. I think typically you inject a <link href=”x”> for css and a <script src=”y”> for the js. How do you propose to add those to the module js?
On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
Hi Carlos, thanks. The issue is with inject_html in modules on IE, dialogPolyfill.js just happened to be the target src here. I’ve been searching the net for solutions on IE and I think the trick is to append elements instead of changing the inner html. I see two options of transpiling <inject_html> that would work on IE:
1. Parse the <inject_html> contents in the compiler and create js that would work for IE. Difficult.
2. Replace each line in <inject_html> with dummy elements and change their outerHTML to match each line contents. This one looks easier, but I seem to remember a thread where we were trying to eliminate use of outerHTML.
Any thoughts are welcome.
From: Carlos Rovira<ma...@apache.org>
Sent: Monday, May 11, 2020 6:06 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: Modules in IE
Hi Yishay,
talking without a huge analisys of the problem. I think Jewel Alert works
ok in IE11 so that should mean dialogpolyfil is loading ok. if not the case
something broke recently since I checked that in TDJ and other apps we did.
Anyway, the commit you state is just to give the support we needed. I
didn't tested in IE11, so don't know if we support it. Normally IE11 use to
require
some special way of writing the code for some particular things, so I think
the way to solve this is:
1.- search in SOF or other sources how IE11 expect scripts to be added
dynamically
2.- upgrade the compiler code to use that way with that considerations to
make it IE11 compatible and check if that works for IE11 and rest of
browsers.
sorry to not be able to say much more, but I'm these days with few time
Thanks
El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<yi...@hotmail.com>)
escribió:
> Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in compiler code
> doesn’t work for IE11. Any ideas on how to fix this?
>
> From: Yishay Weiss<ma...@hotmail.com>
> Sent: Monday, May 11, 2020 4:52 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: RE: Modules in IE
>
> These lines in dialogPolyfill.as
>
> * <inject_html>
> * <script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> "></script>
>
> get transpiled to
>
> document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> "></script>'
>
> But that’s making IE11 fail in loading the module. It doesn’t matter what
> the src is, IE will silently fail. For example, I’m getting the same result
> if I replace the above with
>
> document.head.innerHTML += '<script></script>'
>
>
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:35:55 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=UhWgHnDOQVBBCGVW9RI3gwCcxHZcBcYjNu9bfmNEqbI%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=k5fxV4D7kTCIKILQxTYLYkIlTG29sSNaJiJ0gdnXkXM%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:36 PM
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=90IzQjbCvQTqLKnJv4B0q0xP8L7tKRBcGZkeLzsv1hU%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=evkgF0%2BsdYs2Irz1Jigsgmn6Yq4IS7e4LLvGCJ4EReY%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
Carlos Rovira
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=L0ya5B62P40fyCYZolQxaDCkYF0cbmuDHZhURTCXLPw%3D&reserved=0
RE: Modules in IE
Posted by Yishay Weiss <yi...@hotmail.com>.
>What if we abandon "inject_html" and go with "inject_script" instead? Then when adding to the html output, each >script would be wrapped with a <script> tag, but for modules the code could be added to the main module .js file.
I’m not sure about this. I think typically you inject a <link href=”x”> for css and a <script src=”y”> for the js. How do you propose to add those to the module js?
On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
Hi Carlos, thanks. The issue is with inject_html in modules on IE, dialogPolyfill.js just happened to be the target src here. I’ve been searching the net for solutions on IE and I think the trick is to append elements instead of changing the inner html. I see two options of transpiling <inject_html> that would work on IE:
1. Parse the <inject_html> contents in the compiler and create js that would work for IE. Difficult.
2. Replace each line in <inject_html> with dummy elements and change their outerHTML to match each line contents. This one looks easier, but I seem to remember a thread where we were trying to eliminate use of outerHTML.
Any thoughts are welcome.
From: Carlos Rovira<ma...@apache.org>
Sent: Monday, May 11, 2020 6:06 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: Modules in IE
Hi Yishay,
talking without a huge analisys of the problem. I think Jewel Alert works
ok in IE11 so that should mean dialogpolyfil is loading ok. if not the case
something broke recently since I checked that in TDJ and other apps we did.
Anyway, the commit you state is just to give the support we needed. I
didn't tested in IE11, so don't know if we support it. Normally IE11 use to
require
some special way of writing the code for some particular things, so I think
the way to solve this is:
1.- search in SOF or other sources how IE11 expect scripts to be added
dynamically
2.- upgrade the compiler code to use that way with that considerations to
make it IE11 compatible and check if that works for IE11 and rest of
browsers.
sorry to not be able to say much more, but I'm these days with few time
Thanks
El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<yi...@hotmail.com>)
escribió:
> Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in compiler code
> doesn’t work for IE11. Any ideas on how to fix this?
>
> From: Yishay Weiss<ma...@hotmail.com>
> Sent: Monday, May 11, 2020 4:52 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: RE: Modules in IE
>
> These lines in dialogPolyfill.as
>
> * <inject_html>
> * <script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> "></script>
>
> get transpiled to
>
> document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> "></script>'
>
> But that’s making IE11 fail in loading the module. It doesn’t matter what
> the src is, IE will silently fail. For example, I’m getting the same result
> if I replace the above with
>
> document.head.innerHTML += '<script></script>'
>
>
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:35:55 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=UhWgHnDOQVBBCGVW9RI3gwCcxHZcBcYjNu9bfmNEqbI%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=k5fxV4D7kTCIKILQxTYLYkIlTG29sSNaJiJ0gdnXkXM%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:36 PM
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=90IzQjbCvQTqLKnJv4B0q0xP8L7tKRBcGZkeLzsv1hU%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=evkgF0%2BsdYs2Irz1Jigsgmn6Yq4IS7e4LLvGCJ4EReY%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
Carlos Rovira
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=L0ya5B62P40fyCYZolQxaDCkYF0cbmuDHZhURTCXLPw%3D&reserved=0
Re: Modules in IE
Posted by Alex Harui <ah...@adobe.com.INVALID>.
On 5/15/20, 7:35 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> Also, it is possible that inject_html is being overused (…) a static initializer could bring in the code
Do we have an example of static initializers working in Royale? I tried adding some code in curly brackets after the class declaration but I didn’t see it transpiled.
I was thinking Flex-like static initializers, not bare-code initializers. The Flex pattern is:
private static var someStatic = someStaticInitializer();
private static function someStaticInitializer()
{
// code goes here
}
On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
Hi Carlos, thanks. The issue is with inject_html in modules on IE, dialogPolyfill.js just happened to be the target src here. I’ve been searching the net for solutions on IE and I think the trick is to append elements instead of changing the inner html. I see two options of transpiling <inject_html> that would work on IE:
1. Parse the <inject_html> contents in the compiler and create js that would work for IE. Difficult.
2. Replace each line in <inject_html> with dummy elements and change their outerHTML to match each line contents. This one looks easier, but I seem to remember a thread where we were trying to eliminate use of outerHTML.
Any thoughts are welcome.
From: Carlos Rovira<ma...@apache.org>
Sent: Monday, May 11, 2020 6:06 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: Modules in IE
Hi Yishay,
talking without a huge analisys of the problem. I think Jewel Alert works
ok in IE11 so that should mean dialogpolyfil is loading ok. if not the case
something broke recently since I checked that in TDJ and other apps we did.
Anyway, the commit you state is just to give the support we needed. I
didn't tested in IE11, so don't know if we support it. Normally IE11 use to
require
some special way of writing the code for some particular things, so I think
the way to solve this is:
1.- search in SOF or other sources how IE11 expect scripts to be added
dynamically
2.- upgrade the compiler code to use that way with that considerations to
make it IE11 compatible and check if that works for IE11 and rest of
browsers.
sorry to not be able to say much more, but I'm these days with few time
Thanks
El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<yi...@hotmail.com>)
escribió:
> Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in compiler code
> doesn’t work for IE11. Any ideas on how to fix this?
>
> From: Yishay Weiss<ma...@hotmail.com>
> Sent: Monday, May 11, 2020 4:52 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: RE: Modules in IE
>
> These lines in dialogPolyfill.as
>
> * <inject_html>
> * <script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cec07f8ff0d0f4954a17508d7f8dd343a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637251501266277679&sdata=D4avRkHF1%2B4vLa4E9NCnt%2Bu%2BeTjqwHPr%2BpN1oU1eQtA%3D&reserved=0
> "></script>
>
> get transpiled to
>
> document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cec07f8ff0d0f4954a17508d7f8dd343a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637251501266277679&sdata=D4avRkHF1%2B4vLa4E9NCnt%2Bu%2BeTjqwHPr%2BpN1oU1eQtA%3D&reserved=0
> "></script>'
>
> But that’s making IE11 fail in loading the module. It doesn’t matter what
> the src is, IE will silently fail. For example, I’m getting the same result
> if I replace the above with
>
> document.head.innerHTML += '<script></script>'
>
>
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:35:55 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cec07f8ff0d0f4954a17508d7f8dd343a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637251501266287555&sdata=8GuFutzP3tY2MXqTSaSTrpzhxvxLHBf7x%2BHpjcgp%2FYA%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cec07f8ff0d0f4954a17508d7f8dd343a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637251501266287555&sdata=8GuFutzP3tY2MXqTSaSTrpzhxvxLHBf7x%2BHpjcgp%2FYA%3D&reserved=0
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cec07f8ff0d0f4954a17508d7f8dd343a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637251501266287555&sdata=fcgLQZKZMKR2tQ2ww1bj8PBQXrIDPs2RXzQoE1%2FLBgE%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cec07f8ff0d0f4954a17508d7f8dd343a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637251501266287555&sdata=KOVIPzTxLh%2F4oqQQXZgOHR5QNnvLe9OalyZjfavySBQ%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:36 PM
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cec07f8ff0d0f4954a17508d7f8dd343a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637251501266287555&sdata=8GuFutzP3tY2MXqTSaSTrpzhxvxLHBf7x%2BHpjcgp%2FYA%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cec07f8ff0d0f4954a17508d7f8dd343a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637251501266287555&sdata=8GuFutzP3tY2MXqTSaSTrpzhxvxLHBf7x%2BHpjcgp%2FYA%3D&reserved=0
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cec07f8ff0d0f4954a17508d7f8dd343a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637251501266287555&sdata=fcgLQZKZMKR2tQ2ww1bj8PBQXrIDPs2RXzQoE1%2FLBgE%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cec07f8ff0d0f4954a17508d7f8dd343a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637251501266287555&sdata=KOVIPzTxLh%2F4oqQQXZgOHR5QNnvLe9OalyZjfavySBQ%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
Carlos Rovira
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cec07f8ff0d0f4954a17508d7f8dd343a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637251501266287555&sdata=YjFlpDTVGlPtef8Bi9FyQrGVzBzlz1B3WZkOLun3NSI%3D&reserved=0
Re: Modules in IE
Posted by Carlos Rovira <ca...@apache.org>.
+1 to get it working in class too.
I suffer the limitations to just work on constructors, so that will help to
avoid rethinking implementations that should work
El vie., 15 may. 2020 a las 18:26, Alex Harui (<ah...@adobe.com.invalid>)
escribió:
> If you can get it to work on a class or function that's fine with me. I
> only implemented it for constructor because the ASDoc for the constructor
> is retained in the output JS for the publisher to gather and inject. I
> was too lazy to figure out how to retain it for the class ASDoc or function
> ASDoc.
>
> -Alex
>
> On 5/15/20, 9:12 AM, "Josh Tynjala" <jo...@bowlerhat.dev> wrote:
>
> Any chance we can have inject_script work on the class instead of the
> constructor? Ideally, inject_script would work on a function declared
> in a
> package too.
>
> package com.example {
> /**
> * <inject_script>
> * //script here
> * </inject_script>
> */
> public function someFunction():void {}
> }
>
> --
> Josh Tynjala
> Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.dev%2F&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262957154&sdata=277HO8LqQV4%2FF0L1O3P7JKfMGohBnoAltOB3QM2PGZM%3D&reserved=0
> >
>
>
> On Fri, May 15, 2020 at 8:10 AM Yishay Weiss <yi...@hotmail.com>
> wrote:
>
> > Thanks Piotr, I just merged.
> >
> >
> >
> > Carlos, sorry to create work for you but can you updated the
> > documentation? [1]. Instead of
> >
> >
> >
> > * <inject_html>
> >
> > * <script src="//
> > cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/highlight.min.js
> > "></script>
> >
> > * <link rel="stylesheet" title="Atom One Dark" href="//
> >
> cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/atom-one-dark.min.css
> > ">
> >
> > * </inject_html>
> >
> >
> >
> > It should be
> >
> >
> >
> > * <inject_script>
> >
> > * var script = document.createElement("script");
> >
> > * script.setAttribute("src", "
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fhighlight.js%2F9.12.0%2Fhighlight.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262957154&sdata=Pu%2FcFKUNLx8VIAy6wgk8teI1WaTCKpLmkhNpDIRS5uY%3D&reserved=0
> > ");
> >
> > * document.head.appendChild(script);
> >
> > * var link = document.createElement("link");
> >
> > * link.setAttribute("rel", "stylesheet");
> >
> > * link.setAttribute("title", "Atom One Dark");
> >
> > * link.setAttribute("type", "text/css");
> >
> > * link.setAttribute("href", "
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fhighlight.js%2F9.12.0%2Fstyles%2Fatom-one-dark.min.css&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262957154&sdata=6J5twy%2Fvr28yvyc%2BWnXQ2PbtrgdRAlRP0WdVK5fbgzU%3D&reserved=0
> > ");
> >
> > * document.head.appendChild(link);
> >
> > * </inject_script>
> >
> >
> >
> > And
> >
> > “An inject_html directive declared in the constructor…”
> >
> > should be replaced with
> >
> > “An inject_script directive declared in the constructor…”.
> >
> >
> >
> > Thanks.
> >
> >
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fusing-external-javascript-libraries-in-apache-royale%2F&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262957154&sdata=wYxszNKkKnkF3bIy1Xmyqt3vQSqxippe3vwz4im8q5Q%3D&reserved=0
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > *From:* Piotr Zarzycki <pi...@gmail.com>
> > *Sent:* Friday, May 15, 2020 5:41:07 PM
> > *To:* Apache Royale Development <de...@royale.apache.org>
> > *Subject:* Re: Modules in IE
> >
> >
> >
> > Yishay,
> >
> > I do not have any problems with that. I just missed point where you
> have
> > said that is being removed. It's working so +1 from my sight on
> merge this.
> >
> > Thanks,
> > Piotr
> >
> > pt., 15 maj 2020 o 16:35 Yishay Weiss <yi...@hotmail.com>
> napisał(a):
> >
> > >
> > >
> > > > Also, it is possible that inject_html is being overused (…) a
> static
> > > initializer could bring in the code
> > > Do we have an example of static initializers working in Royale? I
> tried
> > > adding some code in curly brackets after the class declaration but
> I
> > didn’t
> > > see it transpiled.
> > >
> > > On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> > >
> > > Hi Carlos, thanks. The issue is with inject_html in modules on
> IE,
> > > dialogPolyfill.js just happened to be the target src here. I’ve
> been
> > > searching the net for solutions on IE and I think the trick is to
> append
> > > elements instead of changing the inner html. I see two options of
> > > transpiling <inject_html> that would work on IE:
> > >
> > >
> > > 1. Parse the <inject_html> contents in the compiler and
> create js
> > > that would work for IE. Difficult.
> > > 2. Replace each line in <inject_html> with dummy elements
> and
> > > change their outerHTML to match each line contents. This one looks
> > easier,
> > > but I seem to remember a thread where we were trying to eliminate
> use of
> > > outerHTML.
> > >
> > >
> > > Any thoughts are welcome.
> > >
> > > From: Carlos Rovira<mailto:carlosrovira@apache.org
> > <ca...@apache.org>>
> > > Sent: Monday, May 11, 2020 6:06 PM
> > > To: Apache Royale Development<mailto:dev@royale.apache.org
> > <de...@royale.apache.org>>
> > > Subject: Re: Modules in IE
> > >
> > > Hi Yishay,
> > >
> > > talking without a huge analisys of the problem. I think Jewel
> Alert
> > > works
> > > ok in IE11 so that should mean dialogpolyfil is loading ok. if
> not
> > the
> > > case
> > > something broke recently since I checked that in TDJ and other
> apps
> > we
> > > did.
> > >
> > > Anyway, the commit you state is just to give the support we
> needed. I
> > > didn't tested in IE11, so don't know if we support it.
> Normally IE11
> > > use to
> > > require
> > > some special way of writing the code for some particular
> things, so I
> > > think
> > > the way to solve this is:
> > >
> > > 1.- search in SOF or other sources how IE11 expect scripts to
> be
> > added
> > > dynamically
> > > 2.- upgrade the compiler code to use that way with that
> > considerations
> > > to
> > > make it IE11 compatible and check if that works for IE11 and
> rest of
> > > browsers.
> > >
> > > sorry to not be able to say much more, but I'm these days with
> few
> > time
> > >
> > > Thanks
> > >
> > >
> > >
> > > El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<
> > > yishayjobs@hotmail.com>)
> > > escribió:
> > >
> > > > Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in
> > compiler
> > > code
> > > > doesn’t work for IE11. Any ideas on how to fix this?
> > > >
> > > > From: Yishay Weiss<mailto:yishayjobs@hotmail.com
> > <yi...@hotmail.com>>
> > > > Sent: Monday, May 11, 2020 4:52 PM
> > > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > > Subject: RE: Modules in IE
> > > >
> > > > These lines in dialogPolyfill.as
> > > >
> > > > * <inject_html>
> > > > * <script src="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262957154&sdata=IIn1im6gb6dGn%2Fo4UMuB2HGqaMjZpZ9PEMykrQ1Yj2o%3D&reserved=0
> > > > "></script>
> > > >
> > > > get transpiled to
> > > >
> > > > document.head.innerHTML += '<script src="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262957154&sdata=IIn1im6gb6dGn%2Fo4UMuB2HGqaMjZpZ9PEMykrQ1Yj2o%3D&reserved=0
> > > > "></script>'
> > > >
> > > > But that’s making IE11 fail in loading the module. It doesn’t
> > matter
> > > what
> > > > the src is, IE will silently fail. For example, I’m getting
> the
> > same
> > > result
> > > > if I replace the above with
> > > >
> > > > document.head.innerHTML += '<script></script>'
> > > >
> > > >
> > > >
> > > >
> > > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > > Sent: Sunday, May 10, 2020 7:35:55 PM
> > > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > Does dialog-polyfill load correctly? Does it muck with the
> window
> > > object?
> > > >
> > > > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> > wrote:
> > > >
> > > > Test1.js isn’t different, but Test1_deps.js is.
> > > >
> > > > diff --git
> "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > > index 73eccbe..3e1a8a7 100644
> > > > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > > @@ -211,4 +211,4 @@
> > > >
> > >
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > > > ['org
> > > > goog.addDependency('../../../XML.js', ['XML'], []);
> > > >
> > > > goog.require('Test1');
> > > > -document.head.innerHTML += '<script src="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262957154&sdata=IIn1im6gb6dGn%2Fo4UMuB2HGqaMjZpZ9PEMykrQ1Yj2o%3D&reserved=0
> > > > "></script<
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262957154&sdata=IIn1im6gb6dGn%2Fo4UMuB2HGqaMjZpZ9PEMykrQ1Yj2o%3D&reserved=0
> > > > >>';document.head.innerHTM
> > > > L += '<link rel="stylesheet" type="text/css" href="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262967150&sdata=2E0AJYT8SOZw%2F0sykIBzn4qR%2BHPiPiSkJsCgWZy%2BEM4%3D&reserved=0
> > > > ">';
> > > > +
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Sunday, May 10, 2020 6:39 PM
> > > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > Interesting. Just adding import shouldn't affect the
> output.
> > > What is
> > > > the difference between Test1.js with and without that import
> > > statement?
> > > >
> > > > -Alex
> > > >
> > > > On 5/10/20, 8:31 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > > wrote:
> > > >
> > > > I’ve narrowed it down to usage of mx.controls.Alert.
> Test
> > > case is
> > > > included in this issue [1].
> > > >
> > > > [1]
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262967150&sdata=yzMwuCCiZGatJnXUQhkTxuJeBDTRnIlwV2t43tWkTCI%3D&reserved=0
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Thursday, May 7, 2020 10:35 PM
> > > > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > I think you can verify by debugging in some other
> browser
> > > and see
> > > > if breakpoints get set.
> > > >
> > > > A common “bug” in Flex modules was to reference and
> link
> > the
> > > > module class into the loading app. I have no idea what will
> happen
> > > if you
> > > > have such a situation in Royale. You can look at the
> loading app’s
> > > > link-report to see if the module (Test1) is linked in the
> app and
> > > probably
> > > > see if Test1.js is in the output of the app if you start
> clean and
> > > do not
> > > > compile the module.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > From: Yishay Weiss <yi...@hotmail.com>
> > > > Reply-To: "dev@royale.apache.org" <
> dev@royale.apache.org>
> > > > Date: Thursday, May 7, 2020 at 12:26 PM
> > > > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > > Subject: RE: Modules in IE
> > > >
> > > > url is
> > > >
> > > >
> > >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js
> > >>>>>
> > > >
> > > > I don’t see errors other than
> > > >
> > > > SEC7113: CSS was ignored due to mime type mismatch
> > > >
> > > > But I don’t think that’s it.
> > > >
> > > > I put a debugger; statement on the first line of the
> src
> > > which
> > > > never kicks.
> > > >
> > > >
> > > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > What is the src (url) for that script? Were there
> any
> > errors
> > > > loading and running it? Are the other Royale
> packages/classes in
> > the
> > > > "window" object?
> > > >
> > > > One scenario I thought of is that some bug or
> something
> > else
> > > > creates a "window" property at the global window causing our
> > package
> > > lookup
> > > > to be off.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com
> > >
> > > wrote:
> > > >
> > > > In my example <script> element is there but it’s
> never
> > > loaded
> > > > on IE. I can confirm ModuleExamle works.
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Sunday, May 3, 2020 9:31 AM
> > > > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > > > Subject: Re: Modules in IE
> > > >
> > > > I just ran examples/royale/ModuleExample in IE
> and it
> > > worked.
> > > > Does it work for you?
> > > > In the debugger, window.Module and window.MainApp
> > > resolve to
> > > > functions. window.org is an object with an apache property.
> > > > In the DOM Explorer, there should be tons of
> <script>
> > > tags in
> > > > the head. Near the end of the list should be the script for
> the
> > .js
> > > file
> > > > for the module.
> > > > Do you see any exceptions? ModuleExample works
> without
> > > errors.
> > > >
> > > > -Alex
> > > >
> > > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com>
> > > > wrote:
> > > >
> > > > 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:
> aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Thursday, April 30, 2020 6:29 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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:
> > aharui@adobe.com.INVALID
> > > >
> > > > Sent: Thursday, April 30, 2020 12:00 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org
> > > > >
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Wednesday, May 6, 2020 7:58 PM
> > > > Subject: Re: Modules in IE
> > > >
> > > > What is the src (url) for that script? Were there
> any
> > errors
> > > > loading and running it? Are the other Royale
> packages/classes in
> > the
> > > > "window" object?
> > > >
> > > > One scenario I thought of is that some bug or
> something
> > else
> > > > creates a "window" property at the global window causing our
> > package
> > > lookup
> > > > to be off.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com
> > >
> > > wrote:
> > > >
> > > > In my example <script> element is there but it’s
> never
> > > loaded
> > > > on IE. I can confirm ModuleExamle works.
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Sunday, May 3, 2020 9:31 AM
> > > > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > > > Subject: Re: Modules in IE
> > > >
> > > > I just ran examples/royale/ModuleExample in IE
> and it
> > > worked.
> > > > Does it work for you?
> > > > In the debugger, window.Module and window.MainApp
> > > resolve to
> > > > functions. window.org is an object with an apache property.
> > > > In the DOM Explorer, there should be tons of
> <script>
> > > tags in
> > > > the head. Near the end of the list should be the script for
> the
> > .js
> > > file
> > > > for the module.
> > > > Do you see any exceptions? ModuleExample works
> without
> > > errors.
> > > >
> > > > -Alex
> > > >
> > > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com>
> > > > wrote:
> > > >
> > > > 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:
> aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Thursday, April 30, 2020 6:29 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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:
> > aharui@adobe.com.INVALID
> > > >
> > > > Sent: Thursday, April 30, 2020 12:00 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org
> > > > >
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Sunday, May 10, 2020 7:36 PM
> > > > Subject: Re: Modules in IE
> > > >
> > > > Does dialog-polyfill load correctly? Does it muck with the
> window
> > > object?
> > > >
> > > > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> > wrote:
> > > >
> > > > Test1.js isn’t different, but Test1_deps.js is.
> > > >
> > > > diff --git
> "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > > index 73eccbe..3e1a8a7 100644
> > > > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > > @@ -211,4 +211,4 @@
> > > >
> > >
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > > > ['org
> > > > goog.addDependency('../../../XML.js', ['XML'], []);
> > > >
> > > > goog.require('Test1');
> > > > -document.head.innerHTML += '<script src="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262967150&sdata=dhlOCaRFxImKQS7jqvCntHA3lAdeGUtm%2FQbuG9JsSHk%3D&reserved=0
> > > > "></script<
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262967150&sdata=dhlOCaRFxImKQS7jqvCntHA3lAdeGUtm%2FQbuG9JsSHk%3D&reserved=0
> > > > >>';document.head.innerHTM
> > > > L += '<link rel="stylesheet" type="text/css" href="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262967150&sdata=2E0AJYT8SOZw%2F0sykIBzn4qR%2BHPiPiSkJsCgWZy%2BEM4%3D&reserved=0
> > > > ">';
> > > > +
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Sunday, May 10, 2020 6:39 PM
> > > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > Interesting. Just adding import shouldn't affect the
> output.
> > > What is
> > > > the difference between Test1.js with and without that import
> > > statement?
> > > >
> > > > -Alex
> > > >
> > > > On 5/10/20, 8:31 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > > wrote:
> > > >
> > > > I’ve narrowed it down to usage of mx.controls.Alert.
> Test
> > > case is
> > > > included in this issue [1].
> > > >
> > > > [1]
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262967150&sdata=yzMwuCCiZGatJnXUQhkTxuJeBDTRnIlwV2t43tWkTCI%3D&reserved=0
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Thursday, May 7, 2020 10:35 PM
> > > > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > I think you can verify by debugging in some other
> browser
> > > and see
> > > > if breakpoints get set.
> > > >
> > > > A common “bug” in Flex modules was to reference and
> link
> > the
> > > > module class into the loading app. I have no idea what will
> happen
> > > if you
> > > > have such a situation in Royale. You can look at the
> loading app’s
> > > > link-report to see if the module (Test1) is linked in the
> app and
> > > probably
> > > > see if Test1.js is in the output of the app if you start
> clean and
> > > do not
> > > > compile the module.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > From: Yishay Weiss <yi...@hotmail.com>
> > > > Reply-To: "dev@royale.apache.org" <
> dev@royale.apache.org>
> > > > Date: Thursday, May 7, 2020 at 12:26 PM
> > > > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > > Subject: RE: Modules in IE
> > > >
> > > > url is
> > > >
> > > >
> > >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js
> > >>>>>
> > > >
> > > > I don’t see errors other than
> > > >
> > > > SEC7113: CSS was ignored due to mime type mismatch
> > > >
> > > > But I don’t think that’s it.
> > > >
> > > > I put a debugger; statement on the first line of the
> src
> > > which
> > > > never kicks.
> > > >
> > > >
> > > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > What is the src (url) for that script? Were there
> any
> > errors
> > > > loading and running it? Are the other Royale
> packages/classes in
> > the
> > > > "window" object?
> > > >
> > > > One scenario I thought of is that some bug or
> something
> > else
> > > > creates a "window" property at the global window causing our
> > package
> > > lookup
> > > > to be off.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com
> > >
> > > wrote:
> > > >
> > > > In my example <script> element is there but it’s
> never
> > > loaded
> > > > on IE. I can confirm ModuleExamle works.
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Sunday, May 3, 2020 9:31 AM
> > > > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > > > Subject: Re: Modules in IE
> > > >
> > > > I just ran examples/royale/ModuleExample in IE
> and it
> > > worked.
> > > > Does it work for you?
> > > > In the debugger, window.Module and window.MainApp
> > > resolve to
> > > > functions. window.org is an object with an apache property.
> > > > In the DOM Explorer, there should be tons of
> <script>
> > > tags in
> > > > the head. Near the end of the list should be the script for
> the
> > .js
> > > file
> > > > for the module.
> > > > Do you see any exceptions? ModuleExample works
> without
> > > errors.
> > > >
> > > > -Alex
> > > >
> > > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com>
> > > > wrote:
> > > >
> > > > 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:
> aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Thursday, April 30, 2020 6:29 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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:
> > aharui@adobe.com.INVALID
> > > >
> > > > Sent: Thursday, April 30, 2020 12:00 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org
> > > > >
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Wednesday, May 6, 2020 7:58 PM
> > > > Subject: Re: Modules in IE
> > > >
> > > > What is the src (url) for that script? Were there
> any
> > errors
> > > > loading and running it? Are the other Royale
> packages/classes in
> > the
> > > > "window" object?
> > > >
> > > > One scenario I thought of is that some bug or
> something
> > else
> > > > creates a "window" property at the global window causing our
> > package
> > > lookup
> > > > to be off.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com
> > >
> > > wrote:
> > > >
> > > > In my example <script> element is there but it’s
> never
> > > loaded
> > > > on IE. I can confirm ModuleExamle works.
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Sunday, May 3, 2020 9:31 AM
> > > > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > > > Subject: Re: Modules in IE
> > > >
> > > > I just ran examples/royale/ModuleExample in IE
> and it
> > > worked.
> > > > Does it work for you?
> > > > In the debugger, window.Module and window.MainApp
> > > resolve to
> > > > functions. window.org is an object with an apache property.
> > > > In the DOM Explorer, there should be tons of
> <script>
> > > tags in
> > > > the head. Near the end of the list should be the script for
> the
> > .js
> > > file
> > > > for the module.
> > > > Do you see any exceptions? ModuleExample works
> without
> > > errors.
> > > >
> > > > -Alex
> > > >
> > > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com>
> > > > wrote:
> > > >
> > > > 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:
> aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Thursday, April 30, 2020 6:29 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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:
> > aharui@adobe.com.INVALID
> > > >
> > > > Sent: Thursday, April 30, 2020 12:00 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org
> > > > >
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > > --
> > > Carlos Rovira
> > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262967150&sdata=LG9g8nnt5baOySmNOwdDTjl%2FFxo30Pj9pD%2FaGjFHN1A%3D&reserved=0
> > >
> > >
> > >
> > >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262977136&sdata=N8aC0euuYyFSu1QiwupYMFRH1NwrYZOTLoomzXxCPkc%3D&reserved=0
> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262977136&sdata=N8aC0euuYyFSu1QiwupYMFRH1NwrYZOTLoomzXxCPkc%3D&reserved=0
> >*
> >
> > *From: *Piotr Zarzycki <pi...@gmail.com>
> > *Sent: *Friday, May 15, 2020 5:41 PM
> > *To: *Apache Royale Development <de...@royale.apache.org>
> > *Subject: *Re: Modules in IE
> >
> >
> >
> > Yishay,
> >
> > I do not have any problems with that. I just missed point where you
> have
> > said that is being removed. It's working so +1 from my sight on
> merge this.
> >
> > Thanks,
> > Piotr
> >
> > pt., 15 maj 2020 o 16:35 Yishay Weiss <yi...@hotmail.com>
> napisał(a):
> >
> > >
> > >
> > > > Also, it is possible that inject_html is being overused (…) a
> static
> > > initializer could bring in the code
> > > Do we have an example of static initializers working in Royale? I
> tried
> > > adding some code in curly brackets after the class declaration but
> I
> > didn’t
> > > see it transpiled.
> > >
> > > On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> > >
> > > Hi Carlos, thanks. The issue is with inject_html in modules on
> IE,
> > > dialogPolyfill.js just happened to be the target src here. I’ve
> been
> > > searching the net for solutions on IE and I think the trick is to
> append
> > > elements instead of changing the inner html. I see two options of
> > > transpiling <inject_html> that would work on IE:
> > >
> > >
> > > 1. Parse the <inject_html> contents in the compiler and
> create js
> > > that would work for IE. Difficult.
> > > 2. Replace each line in <inject_html> with dummy elements
> and
> > > change their outerHTML to match each line contents. This one looks
> > easier,
> > > but I seem to remember a thread where we were trying to eliminate
> use of
> > > outerHTML.
> > >
> > >
> > > Any thoughts are welcome.
> > >
> > > From: Carlos Rovira<mailto:carlosrovira@apache.org
> > <ca...@apache.org>>
> > > Sent: Monday, May 11, 2020 6:06 PM
> > > To: Apache Royale Development<mailto:dev@royale.apache.org
> > <de...@royale.apache.org>>
> > > Subject: Re: Modules in IE
> > >
> > > Hi Yishay,
> > >
> > > talking without a huge analisys of the problem. I think Jewel
> Alert
> > > works
> > > ok in IE11 so that should mean dialogpolyfil is loading ok. if
> not
> > the
> > > case
> > > something broke recently since I checked that in TDJ and other
> apps
> > we
> > > did.
> > >
> > > Anyway, the commit you state is just to give the support we
> needed. I
> > > didn't tested in IE11, so don't know if we support it.
> Normally IE11
> > > use to
> > > require
> > > some special way of writing the code for some particular
> things, so I
> > > think
> > > the way to solve this is:
> > >
> > > 1.- search in SOF or other sources how IE11 expect scripts to
> be
> > added
> > > dynamically
> > > 2.- upgrade the compiler code to use that way with that
> > considerations
> > > to
> > > make it IE11 compatible and check if that works for IE11 and
> rest of
> > > browsers.
> > >
> > > sorry to not be able to say much more, but I'm these days with
> few
> > time
> > >
> > > Thanks
> > >
> > >
> > >
> > > El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<
> > > yishayjobs@hotmail.com>)
> > > escribió:
> > >
> > > > Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in
> > compiler
> > > code
> > > > doesn’t work for IE11. Any ideas on how to fix this?
> > > >
> > > > From: Yishay Weiss<mailto:yishayjobs@hotmail.com
> > <yi...@hotmail.com>>
> > > > Sent: Monday, May 11, 2020 4:52 PM
> > > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > > Subject: RE: Modules in IE
> > > >
> > > > These lines in dialogPolyfill.as
> > > >
> > > > * <inject_html>
> > > > * <script src="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262977136&sdata=67GEsWSZR7UoSl6774E53wr%2BdItmFimmWQ7Vzlt84Ow%3D&reserved=0
> > > > "></script>
> > > >
> > > > get transpiled to
> > > >
> > > > document.head.innerHTML += '<script src="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262977136&sdata=67GEsWSZR7UoSl6774E53wr%2BdItmFimmWQ7Vzlt84Ow%3D&reserved=0
> > > > "></script>'
> > > >
> > > > But that’s making IE11 fail in loading the module. It doesn’t
> > matter
> > > what
> > > > the src is, IE will silently fail. For example, I’m getting
> the
> > same
> > > result
> > > > if I replace the above with
> > > >
> > > > document.head.innerHTML += '<script></script>'
> > > >
> > > >
> > > >
> > > >
> > > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > > Sent: Sunday, May 10, 2020 7:35:55 PM
> > > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > Does dialog-polyfill load correctly? Does it muck with the
> window
> > > object?
> > > >
> > > > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> > wrote:
> > > >
> > > > Test1.js isn’t different, but Test1_deps.js is.
> > > >
> > > > diff --git
> "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > > index 73eccbe..3e1a8a7 100644
> > > > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > > @@ -211,4 +211,4 @@
> > > >
> > >
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > > > ['org
> > > > goog.addDependency('../../../XML.js', ['XML'], []);
> > > >
> > > > goog.require('Test1');
> > > > -document.head.innerHTML += '<script src="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262977136&sdata=67GEsWSZR7UoSl6774E53wr%2BdItmFimmWQ7Vzlt84Ow%3D&reserved=0
> > > > "></script<
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262977136&sdata=67GEsWSZR7UoSl6774E53wr%2BdItmFimmWQ7Vzlt84Ow%3D&reserved=0
> > > > >>';document.head.innerHTM
> > > > L += '<link rel="stylesheet" type="text/css" href="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262977136&sdata=bJoOT9dd%2Fqqcs5MziT4MtxL6DRqzBYHtXg%2FjapeNEbo%3D&reserved=0
> > > > ">';
> > > > +
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Sunday, May 10, 2020 6:39 PM
> > > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > Interesting. Just adding import shouldn't affect the
> output.
> > > What is
> > > > the difference between Test1.js with and without that import
> > > statement?
> > > >
> > > > -Alex
> > > >
> > > > On 5/10/20, 8:31 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > > wrote:
> > > >
> > > > I’ve narrowed it down to usage of mx.controls.Alert.
> Test
> > > case is
> > > > included in this issue [1].
> > > >
> > > > [1]
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262977136&sdata=v1SE2dxmwe54n6IWmLXgGSsxa1N5uRgmIEFZ90mAShE%3D&reserved=0
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Thursday, May 7, 2020 10:35 PM
> > > > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > I think you can verify by debugging in some other
> browser
> > > and see
> > > > if breakpoints get set.
> > > >
> > > > A common “bug” in Flex modules was to reference and
> link
> > the
> > > > module class into the loading app. I have no idea what will
> happen
> > > if you
> > > > have such a situation in Royale. You can look at the
> loading app’s
> > > > link-report to see if the module (Test1) is linked in the
> app and
> > > probably
> > > > see if Test1.js is in the output of the app if you start
> clean and
> > > do not
> > > > compile the module.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > From: Yishay Weiss <yi...@hotmail.com>
> > > > Reply-To: "dev@royale.apache.org" <
> dev@royale.apache.org>
> > > > Date: Thursday, May 7, 2020 at 12:26 PM
> > > > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > > Subject: RE: Modules in IE
> > > >
> > > > url is
> > > >
> > > >
> > >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js
> > >>>>>
> > > >
> > > > I don’t see errors other than
> > > >
> > > > SEC7113: CSS was ignored due to mime type mismatch
> > > >
> > > > But I don’t think that’s it.
> > > >
> > > > I put a debugger; statement on the first line of the
> src
> > > which
> > > > never kicks.
> > > >
> > > >
> > > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > What is the src (url) for that script? Were there
> any
> > errors
> > > > loading and running it? Are the other Royale
> packages/classes in
> > the
> > > > "window" object?
> > > >
> > > > One scenario I thought of is that some bug or
> something
> > else
> > > > creates a "window" property at the global window causing our
> > package
> > > lookup
> > > > to be off.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com
> > >
> > > wrote:
> > > >
> > > > In my example <script> element is there but it’s
> never
> > > loaded
> > > > on IE. I can confirm ModuleExamle works.
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Sunday, May 3, 2020 9:31 AM
> > > > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > > > Subject: Re: Modules in IE
> > > >
> > > > I just ran examples/royale/ModuleExample in IE
> and it
> > > worked.
> > > > Does it work for you?
> > > > In the debugger, window.Module and window.MainApp
> > > resolve to
> > > > functions. window.org is an object with an apache property.
> > > > In the DOM Explorer, there should be tons of
> <script>
> > > tags in
> > > > the head. Near the end of the list should be the script for
> the
> > .js
> > > file
> > > > for the module.
> > > > Do you see any exceptions? ModuleExample works
> without
> > > errors.
> > > >
> > > > -Alex
> > > >
> > > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com>
> > > > wrote:
> > > >
> > > > 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:
> aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Thursday, April 30, 2020 6:29 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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:
> > aharui@adobe.com.INVALID
> > > >
> > > > Sent: Thursday, April 30, 2020 12:00 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org
> > > > >
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Wednesday, May 6, 2020 7:58 PM
> > > > Subject: Re: Modules in IE
> > > >
> > > > What is the src (url) for that script? Were there
> any
> > errors
> > > > loading and running it? Are the other Royale
> packages/classes in
> > the
> > > > "window" object?
> > > >
> > > > One scenario I thought of is that some bug or
> something
> > else
> > > > creates a "window" property at the global window causing our
> > package
> > > lookup
> > > > to be off.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com
> > >
> > > wrote:
> > > >
> > > > In my example <script> element is there but it’s
> never
> > > loaded
> > > > on IE. I can confirm ModuleExamle works.
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Sunday, May 3, 2020 9:31 AM
> > > > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > > > Subject: Re: Modules in IE
> > > >
> > > > I just ran examples/royale/ModuleExample in IE
> and it
> > > worked.
> > > > Does it work for you?
> > > > In the debugger, window.Module and window.MainApp
> > > resolve to
> > > > functions. window.org is an object with an apache property.
> > > > In the DOM Explorer, there should be tons of
> <script>
> > > tags in
> > > > the head. Near the end of the list should be the script for
> the
> > .js
> > > file
> > > > for the module.
> > > > Do you see any exceptions? ModuleExample works
> without
> > > errors.
> > > >
> > > > -Alex
> > > >
> > > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com>
> > > > wrote:
> > > >
> > > > 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:
> aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Thursday, April 30, 2020 6:29 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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:
> > aharui@adobe.com.INVALID
> > > >
> > > > Sent: Thursday, April 30, 2020 12:00 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org
> > > > >
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Sunday, May 10, 2020 7:36 PM
> > > > Subject: Re: Modules in IE
> > > >
> > > > Does dialog-polyfill load correctly? Does it muck with the
> window
> > > object?
> > > >
> > > > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> > wrote:
> > > >
> > > > Test1.js isn’t different, but Test1_deps.js is.
> > > >
> > > > diff --git
> "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > > index 73eccbe..3e1a8a7 100644
> > > > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > > @@ -211,4 +211,4 @@
> > > >
> > >
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > > > ['org
> > > > goog.addDependency('../../../XML.js', ['XML'], []);
> > > >
> > > > goog.require('Test1');
> > > > -document.head.innerHTML += '<script src="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262987138&sdata=TGGfD2mJ08463DmSxT3SC3tHTwUaYMlDvKdiq%2BN3cuo%3D&reserved=0
> > > > "></script<
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262987138&sdata=TGGfD2mJ08463DmSxT3SC3tHTwUaYMlDvKdiq%2BN3cuo%3D&reserved=0
> > > > >>';document.head.innerHTM
> > > > L += '<link rel="stylesheet" type="text/css" href="
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262987138&sdata=FAexclRes3j9Bq7f9EVF%2FMYmqotbhKvvwUFC7G0NOFQ%3D&reserved=0
> > > > ">';
> > > > +
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Sunday, May 10, 2020 6:39 PM
> > > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > Interesting. Just adding import shouldn't affect the
> output.
> > > What is
> > > > the difference between Test1.js with and without that import
> > > statement?
> > > >
> > > > -Alex
> > > >
> > > > On 5/10/20, 8:31 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > > wrote:
> > > >
> > > > I’ve narrowed it down to usage of mx.controls.Alert.
> Test
> > > case is
> > > > included in this issue [1].
> > > >
> > > > [1]
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262987138&sdata=KLBwD3V2m0dKjXz43iSF4O%2BRAFRCY7E4Y6H3eB6aumA%3D&reserved=0
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Thursday, May 7, 2020 10:35 PM
> > > > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > I think you can verify by debugging in some other
> browser
> > > and see
> > > > if breakpoints get set.
> > > >
> > > > A common “bug” in Flex modules was to reference and
> link
> > the
> > > > module class into the loading app. I have no idea what will
> happen
> > > if you
> > > > have such a situation in Royale. You can look at the
> loading app’s
> > > > link-report to see if the module (Test1) is linked in the
> app and
> > > probably
> > > > see if Test1.js is in the output of the app if you start
> clean and
> > > do not
> > > > compile the module.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > From: Yishay Weiss <yi...@hotmail.com>
> > > > Reply-To: "dev@royale.apache.org" <
> dev@royale.apache.org>
> > > > Date: Thursday, May 7, 2020 at 12:26 PM
> > > > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > > Subject: RE: Modules in IE
> > > >
> > > > url is
> > > >
> > > >
> > >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js
> > >>>>>
> > > >
> > > > I don’t see errors other than
> > > >
> > > > SEC7113: CSS was ignored due to mime type mismatch
> > > >
> > > > But I don’t think that’s it.
> > > >
> > > > I put a debugger; statement on the first line of the
> src
> > > which
> > > > never kicks.
> > > >
> > > >
> > > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > > Subject: Re: Modules in IE
> > > >
> > > > What is the src (url) for that script? Were there
> any
> > errors
> > > > loading and running it? Are the other Royale
> packages/classes in
> > the
> > > > "window" object?
> > > >
> > > > One scenario I thought of is that some bug or
> something
> > else
> > > > creates a "window" property at the global window causing our
> > package
> > > lookup
> > > > to be off.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com
> > >
> > > wrote:
> > > >
> > > > In my example <script> element is there but it’s
> never
> > > loaded
> > > > on IE. I can confirm ModuleExamle works.
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Sunday, May 3, 2020 9:31 AM
> > > > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > > > Subject: Re: Modules in IE
> > > >
> > > > I just ran examples/royale/ModuleExample in IE
> and it
> > > worked.
> > > > Does it work for you?
> > > > In the debugger, window.Module and window.MainApp
> > > resolve to
> > > > functions. window.org is an object with an apache property.
> > > > In the DOM Explorer, there should be tons of
> <script>
> > > tags in
> > > > the head. Near the end of the list should be the script for
> the
> > .js
> > > file
> > > > for the module.
> > > > Do you see any exceptions? ModuleExample works
> without
> > > errors.
> > > >
> > > > -Alex
> > > >
> > > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com>
> > > > wrote:
> > > >
> > > > 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:
> aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Thursday, April 30, 2020 6:29 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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:
> > aharui@adobe.com.INVALID
> > > >
> > > > Sent: Thursday, April 30, 2020 12:00 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org
> > > > >
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Wednesday, May 6, 2020 7:58 PM
> > > > Subject: Re: Modules in IE
> > > >
> > > > What is the src (url) for that script? Were there
> any
> > errors
> > > > loading and running it? Are the other Royale
> packages/classes in
> > the
> > > > "window" object?
> > > >
> > > > One scenario I thought of is that some bug or
> something
> > else
> > > > creates a "window" property at the global window causing our
> > package
> > > lookup
> > > > to be off.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > On 5/6/20, 8:47 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com
> > >
> > > wrote:
> > > >
> > > > In my example <script> element is there but it’s
> never
> > > loaded
> > > > on IE. I can confirm ModuleExamle works.
> > > >
> > > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Sunday, May 3, 2020 9:31 AM
> > > > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > > > Subject: Re: Modules in IE
> > > >
> > > > I just ran examples/royale/ModuleExample in IE
> and it
> > > worked.
> > > > Does it work for you?
> > > > In the debugger, window.Module and window.MainApp
> > > resolve to
> > > > functions. window.org is an object with an apache property.
> > > > In the DOM Explorer, there should be tons of
> <script>
> > > tags in
> > > > the head. Near the end of the list should be the script for
> the
> > .js
> > > file
> > > > for the module.
> > > > Do you see any exceptions? ModuleExample works
> without
> > > errors.
> > > >
> > > > -Alex
> > > >
> > > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > > yishayjobs@hotmail.com>
> > > > wrote:
> > > >
> > > > 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:
> aharui@adobe.com.INVALID
> > <ah...@adobe.com.INVALID>>
> > > > Sent: Thursday, April 30, 2020 6:29 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org>
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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:
> > aharui@adobe.com.INVALID
> > > >
> > > > Sent: Thursday, April 30, 2020 12:00 AM
> > > > To: dev@royale.apache.org<mailto:
> > > dev@royale.apache.org
> > > > >
> > > > 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" <
> > > > yishayjobs@hotmail.com> 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.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > > --
> > > Carlos Rovira
> > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262987138&sdata=akvITISjPogL8SiGthbXAdAqVAe8%2BX3XvO6nRUosNcI%3D&reserved=0
> > >
> > >
> > >
> > >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262987138&sdata=jcfN4%2FEFLRZ9QkTUqtkaRt7oo%2FQKK4Ak%2B3FfhjlFR3E%3D&reserved=0
> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262987138&sdata=jcfN4%2FEFLRZ9QkTUqtkaRt7oo%2FQKK4Ak%2B3FfhjlFR3E%3D&reserved=0
> >*
> >
> >
> >
>
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Modules in IE
Posted by Alex Harui <ah...@adobe.com.INVALID>.
If you can get it to work on a class or function that's fine with me. I only implemented it for constructor because the ASDoc for the constructor is retained in the output JS for the publisher to gather and inject. I was too lazy to figure out how to retain it for the class ASDoc or function ASDoc.
-Alex
On 5/15/20, 9:12 AM, "Josh Tynjala" <jo...@bowlerhat.dev> wrote:
Any chance we can have inject_script work on the class instead of the
constructor? Ideally, inject_script would work on a function declared in a
package too.
package com.example {
/**
* <inject_script>
* //script here
* </inject_script>
*/
public function someFunction():void {}
}
--
Josh Tynjala
Bowler Hat LLC <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.dev%2F&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262957154&sdata=277HO8LqQV4%2FF0L1O3P7JKfMGohBnoAltOB3QM2PGZM%3D&reserved=0>
On Fri, May 15, 2020 at 8:10 AM Yishay Weiss <yi...@hotmail.com> wrote:
> Thanks Piotr, I just merged.
>
>
>
> Carlos, sorry to create work for you but can you updated the
> documentation? [1]. Instead of
>
>
>
> * <inject_html>
>
> * <script src="//
> cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/highlight.min.js
> "></script>
>
> * <link rel="stylesheet" title="Atom One Dark" href="//
> cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/atom-one-dark.min.css
> ">
>
> * </inject_html>
>
>
>
> It should be
>
>
>
> * <inject_script>
>
> * var script = document.createElement("script");
>
> * script.setAttribute("src", "
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fhighlight.js%2F9.12.0%2Fhighlight.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262957154&sdata=Pu%2FcFKUNLx8VIAy6wgk8teI1WaTCKpLmkhNpDIRS5uY%3D&reserved=0
> ");
>
> * document.head.appendChild(script);
>
> * var link = document.createElement("link");
>
> * link.setAttribute("rel", "stylesheet");
>
> * link.setAttribute("title", "Atom One Dark");
>
> * link.setAttribute("type", "text/css");
>
> * link.setAttribute("href", "
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fhighlight.js%2F9.12.0%2Fstyles%2Fatom-one-dark.min.css&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262957154&sdata=6J5twy%2Fvr28yvyc%2BWnXQ2PbtrgdRAlRP0WdVK5fbgzU%3D&reserved=0
> ");
>
> * document.head.appendChild(link);
>
> * </inject_script>
>
>
>
> And
>
> “An inject_html directive declared in the constructor…”
>
> should be replaced with
>
> “An inject_script directive declared in the constructor…”.
>
>
>
> Thanks.
>
>
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fusing-external-javascript-libraries-in-apache-royale%2F&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262957154&sdata=wYxszNKkKnkF3bIy1Xmyqt3vQSqxippe3vwz4im8q5Q%3D&reserved=0
>
>
>
>
>
>
>
>
>
> *From:* Piotr Zarzycki <pi...@gmail.com>
> *Sent:* Friday, May 15, 2020 5:41:07 PM
> *To:* Apache Royale Development <de...@royale.apache.org>
> *Subject:* Re: Modules in IE
>
>
>
> Yishay,
>
> I do not have any problems with that. I just missed point where you have
> said that is being removed. It's working so +1 from my sight on merge this.
>
> Thanks,
> Piotr
>
> pt., 15 maj 2020 o 16:35 Yishay Weiss <yi...@hotmail.com> napisał(a):
>
> >
> >
> > > Also, it is possible that inject_html is being overused (…) a static
> > initializer could bring in the code
> > Do we have an example of static initializers working in Royale? I tried
> > adding some code in curly brackets after the class declaration but I
> didn’t
> > see it transpiled.
> >
> > On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> >
> > Hi Carlos, thanks. The issue is with inject_html in modules on IE,
> > dialogPolyfill.js just happened to be the target src here. I’ve been
> > searching the net for solutions on IE and I think the trick is to append
> > elements instead of changing the inner html. I see two options of
> > transpiling <inject_html> that would work on IE:
> >
> >
> > 1. Parse the <inject_html> contents in the compiler and create js
> > that would work for IE. Difficult.
> > 2. Replace each line in <inject_html> with dummy elements and
> > change their outerHTML to match each line contents. This one looks
> easier,
> > but I seem to remember a thread where we were trying to eliminate use of
> > outerHTML.
> >
> >
> > Any thoughts are welcome.
> >
> > From: Carlos Rovira<mailto:carlosrovira@apache.org
> <ca...@apache.org>>
> > Sent: Monday, May 11, 2020 6:06 PM
> > To: Apache Royale Development<mailto:dev@royale.apache.org
> <de...@royale.apache.org>>
> > Subject: Re: Modules in IE
> >
> > Hi Yishay,
> >
> > talking without a huge analisys of the problem. I think Jewel Alert
> > works
> > ok in IE11 so that should mean dialogpolyfil is loading ok. if not
> the
> > case
> > something broke recently since I checked that in TDJ and other apps
> we
> > did.
> >
> > Anyway, the commit you state is just to give the support we needed. I
> > didn't tested in IE11, so don't know if we support it. Normally IE11
> > use to
> > require
> > some special way of writing the code for some particular things, so I
> > think
> > the way to solve this is:
> >
> > 1.- search in SOF or other sources how IE11 expect scripts to be
> added
> > dynamically
> > 2.- upgrade the compiler code to use that way with that
> considerations
> > to
> > make it IE11 compatible and check if that works for IE11 and rest of
> > browsers.
> >
> > sorry to not be able to say much more, but I'm these days with few
> time
> >
> > Thanks
> >
> >
> >
> > El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<
> > yishayjobs@hotmail.com>)
> > escribió:
> >
> > > Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in
> compiler
> > code
> > > doesn’t work for IE11. Any ideas on how to fix this?
> > >
> > > From: Yishay Weiss<mailto:yishayjobs@hotmail.com
> <yi...@hotmail.com>>
> > > Sent: Monday, May 11, 2020 4:52 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: RE: Modules in IE
> > >
> > > These lines in dialogPolyfill.as
> > >
> > > * <inject_html>
> > > * <script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262957154&sdata=IIn1im6gb6dGn%2Fo4UMuB2HGqaMjZpZ9PEMykrQ1Yj2o%3D&reserved=0
> > > "></script>
> > >
> > > get transpiled to
> > >
> > > document.head.innerHTML += '<script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262957154&sdata=IIn1im6gb6dGn%2Fo4UMuB2HGqaMjZpZ9PEMykrQ1Yj2o%3D&reserved=0
> > > "></script>'
> > >
> > > But that’s making IE11 fail in loading the module. It doesn’t
> matter
> > what
> > > the src is, IE will silently fail. For example, I’m getting the
> same
> > result
> > > if I replace the above with
> > >
> > > document.head.innerHTML += '<script></script>'
> > >
> > >
> > >
> > >
> > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > Sent: Sunday, May 10, 2020 7:35:55 PM
> > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > Does dialog-polyfill load correctly? Does it muck with the window
> > object?
> > >
> > > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> > >
> > > Test1.js isn’t different, but Test1_deps.js is.
> > >
> > > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > index 73eccbe..3e1a8a7 100644
> > > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > @@ -211,4 +211,4 @@
> > >
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > > ['org
> > > goog.addDependency('../../../XML.js', ['XML'], []);
> > >
> > > goog.require('Test1');
> > > -document.head.innerHTML += '<script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262957154&sdata=IIn1im6gb6dGn%2Fo4UMuB2HGqaMjZpZ9PEMykrQ1Yj2o%3D&reserved=0
> > > "></script<
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262957154&sdata=IIn1im6gb6dGn%2Fo4UMuB2HGqaMjZpZ9PEMykrQ1Yj2o%3D&reserved=0
> > > >>';document.head.innerHTM
> > > L += '<link rel="stylesheet" type="text/css" href="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262967150&sdata=2E0AJYT8SOZw%2F0sykIBzn4qR%2BHPiPiSkJsCgWZy%2BEM4%3D&reserved=0
> > > ">';
> > > +
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 10, 2020 6:39 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > Interesting. Just adding import shouldn't affect the output.
> > What is
> > > the difference between Test1.js with and without that import
> > statement?
> > >
> > > -Alex
> > >
> > > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> > wrote:
> > >
> > > I’ve narrowed it down to usage of mx.controls.Alert. Test
> > case is
> > > included in this issue [1].
> > >
> > > [1]
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262967150&sdata=yzMwuCCiZGatJnXUQhkTxuJeBDTRnIlwV2t43tWkTCI%3D&reserved=0
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, May 7, 2020 10:35 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > I think you can verify by debugging in some other browser
> > and see
> > > if breakpoints get set.
> > >
> > > A common “bug” in Flex modules was to reference and link
> the
> > > module class into the loading app. I have no idea what will happen
> > if you
> > > have such a situation in Royale. You can look at the loading app’s
> > > link-report to see if the module (Test1) is linked in the app and
> > probably
> > > see if Test1.js is in the output of the app if you start clean and
> > do not
> > > compile the module.
> > >
> > > HTH,
> > > -Alex
> > >
> > > From: Yishay Weiss <yi...@hotmail.com>
> > > Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > Date: Thursday, May 7, 2020 at 12:26 PM
> > > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > Subject: RE: Modules in IE
> > >
> > > url is
> > >
> > >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js
> >>>>>
> > >
> > > I don’t see errors other than
> > >
> > > SEC7113: CSS was ignored due to mime type mismatch
> > >
> > > But I don’t think that’s it.
> > >
> > > I put a debugger; statement on the first line of the src
> > which
> > > never kicks.
> > >
> > >
> > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there any
> errors
> > > loading and running it? Are the other Royale packages/classes in
> the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or something
> else
> > > creates a "window" property at the global window causing our
> package
> > lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <yishayjobs@hotmail.com
> >
> > wrote:
> > >
> > > In my example <script> element is there but it’s never
> > loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE and it
> > worked.
> > > Does it work for you?
> > > In the debugger, window.Module and window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache property.
> > > In the DOM Explorer, there should be tons of <script>
> > tags in
> > > the head. Near the end of the list should be the script for the
> .js
> > file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works without
> > errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Wednesday, May 6, 2020 7:58 PM
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there any
> errors
> > > loading and running it? Are the other Royale packages/classes in
> the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or something
> else
> > > creates a "window" property at the global window causing our
> package
> > lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <yishayjobs@hotmail.com
> >
> > wrote:
> > >
> > > In my example <script> element is there but it’s never
> > loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE and it
> > worked.
> > > Does it work for you?
> > > In the debugger, window.Module and window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache property.
> > > In the DOM Explorer, there should be tons of <script>
> > tags in
> > > the head. Near the end of the list should be the script for the
> .js
> > file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works without
> > errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 10, 2020 7:36 PM
> > > Subject: Re: Modules in IE
> > >
> > > Does dialog-polyfill load correctly? Does it muck with the window
> > object?
> > >
> > > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> > >
> > > Test1.js isn’t different, but Test1_deps.js is.
> > >
> > > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > index 73eccbe..3e1a8a7 100644
> > > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > @@ -211,4 +211,4 @@
> > >
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > > ['org
> > > goog.addDependency('../../../XML.js', ['XML'], []);
> > >
> > > goog.require('Test1');
> > > -document.head.innerHTML += '<script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262967150&sdata=dhlOCaRFxImKQS7jqvCntHA3lAdeGUtm%2FQbuG9JsSHk%3D&reserved=0
> > > "></script<
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262967150&sdata=dhlOCaRFxImKQS7jqvCntHA3lAdeGUtm%2FQbuG9JsSHk%3D&reserved=0
> > > >>';document.head.innerHTM
> > > L += '<link rel="stylesheet" type="text/css" href="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262967150&sdata=2E0AJYT8SOZw%2F0sykIBzn4qR%2BHPiPiSkJsCgWZy%2BEM4%3D&reserved=0
> > > ">';
> > > +
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 10, 2020 6:39 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > Interesting. Just adding import shouldn't affect the output.
> > What is
> > > the difference between Test1.js with and without that import
> > statement?
> > >
> > > -Alex
> > >
> > > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> > wrote:
> > >
> > > I’ve narrowed it down to usage of mx.controls.Alert. Test
> > case is
> > > included in this issue [1].
> > >
> > > [1]
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262967150&sdata=yzMwuCCiZGatJnXUQhkTxuJeBDTRnIlwV2t43tWkTCI%3D&reserved=0
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, May 7, 2020 10:35 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > I think you can verify by debugging in some other browser
> > and see
> > > if breakpoints get set.
> > >
> > > A common “bug” in Flex modules was to reference and link
> the
> > > module class into the loading app. I have no idea what will happen
> > if you
> > > have such a situation in Royale. You can look at the loading app’s
> > > link-report to see if the module (Test1) is linked in the app and
> > probably
> > > see if Test1.js is in the output of the app if you start clean and
> > do not
> > > compile the module.
> > >
> > > HTH,
> > > -Alex
> > >
> > > From: Yishay Weiss <yi...@hotmail.com>
> > > Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > Date: Thursday, May 7, 2020 at 12:26 PM
> > > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > Subject: RE: Modules in IE
> > >
> > > url is
> > >
> > >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js
> >>>>>
> > >
> > > I don’t see errors other than
> > >
> > > SEC7113: CSS was ignored due to mime type mismatch
> > >
> > > But I don’t think that’s it.
> > >
> > > I put a debugger; statement on the first line of the src
> > which
> > > never kicks.
> > >
> > >
> > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there any
> errors
> > > loading and running it? Are the other Royale packages/classes in
> the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or something
> else
> > > creates a "window" property at the global window causing our
> package
> > lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <yishayjobs@hotmail.com
> >
> > wrote:
> > >
> > > In my example <script> element is there but it’s never
> > loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE and it
> > worked.
> > > Does it work for you?
> > > In the debugger, window.Module and window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache property.
> > > In the DOM Explorer, there should be tons of <script>
> > tags in
> > > the head. Near the end of the list should be the script for the
> .js
> > file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works without
> > errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Wednesday, May 6, 2020 7:58 PM
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there any
> errors
> > > loading and running it? Are the other Royale packages/classes in
> the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or something
> else
> > > creates a "window" property at the global window causing our
> package
> > lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <yishayjobs@hotmail.com
> >
> > wrote:
> > >
> > > In my example <script> element is there but it’s never
> > loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE and it
> > worked.
> > > Does it work for you?
> > > In the debugger, window.Module and window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache property.
> > > In the DOM Explorer, there should be tons of <script>
> > tags in
> > > the head. Near the end of the list should be the script for the
> .js
> > file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works without
> > errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > --
> > Carlos Rovira
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262967150&sdata=LG9g8nnt5baOySmNOwdDTjl%2FFxo30Pj9pD%2FaGjFHN1A%3D&reserved=0
> >
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262977136&sdata=N8aC0euuYyFSu1QiwupYMFRH1NwrYZOTLoomzXxCPkc%3D&reserved=0
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262977136&sdata=N8aC0euuYyFSu1QiwupYMFRH1NwrYZOTLoomzXxCPkc%3D&reserved=0>*
>
> *From: *Piotr Zarzycki <pi...@gmail.com>
> *Sent: *Friday, May 15, 2020 5:41 PM
> *To: *Apache Royale Development <de...@royale.apache.org>
> *Subject: *Re: Modules in IE
>
>
>
> Yishay,
>
> I do not have any problems with that. I just missed point where you have
> said that is being removed. It's working so +1 from my sight on merge this.
>
> Thanks,
> Piotr
>
> pt., 15 maj 2020 o 16:35 Yishay Weiss <yi...@hotmail.com> napisał(a):
>
> >
> >
> > > Also, it is possible that inject_html is being overused (…) a static
> > initializer could bring in the code
> > Do we have an example of static initializers working in Royale? I tried
> > adding some code in curly brackets after the class declaration but I
> didn’t
> > see it transpiled.
> >
> > On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> >
> > Hi Carlos, thanks. The issue is with inject_html in modules on IE,
> > dialogPolyfill.js just happened to be the target src here. I’ve been
> > searching the net for solutions on IE and I think the trick is to append
> > elements instead of changing the inner html. I see two options of
> > transpiling <inject_html> that would work on IE:
> >
> >
> > 1. Parse the <inject_html> contents in the compiler and create js
> > that would work for IE. Difficult.
> > 2. Replace each line in <inject_html> with dummy elements and
> > change their outerHTML to match each line contents. This one looks
> easier,
> > but I seem to remember a thread where we were trying to eliminate use of
> > outerHTML.
> >
> >
> > Any thoughts are welcome.
> >
> > From: Carlos Rovira<mailto:carlosrovira@apache.org
> <ca...@apache.org>>
> > Sent: Monday, May 11, 2020 6:06 PM
> > To: Apache Royale Development<mailto:dev@royale.apache.org
> <de...@royale.apache.org>>
> > Subject: Re: Modules in IE
> >
> > Hi Yishay,
> >
> > talking without a huge analisys of the problem. I think Jewel Alert
> > works
> > ok in IE11 so that should mean dialogpolyfil is loading ok. if not
> the
> > case
> > something broke recently since I checked that in TDJ and other apps
> we
> > did.
> >
> > Anyway, the commit you state is just to give the support we needed. I
> > didn't tested in IE11, so don't know if we support it. Normally IE11
> > use to
> > require
> > some special way of writing the code for some particular things, so I
> > think
> > the way to solve this is:
> >
> > 1.- search in SOF or other sources how IE11 expect scripts to be
> added
> > dynamically
> > 2.- upgrade the compiler code to use that way with that
> considerations
> > to
> > make it IE11 compatible and check if that works for IE11 and rest of
> > browsers.
> >
> > sorry to not be able to say much more, but I'm these days with few
> time
> >
> > Thanks
> >
> >
> >
> > El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<
> > yishayjobs@hotmail.com>)
> > escribió:
> >
> > > Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in
> compiler
> > code
> > > doesn’t work for IE11. Any ideas on how to fix this?
> > >
> > > From: Yishay Weiss<mailto:yishayjobs@hotmail.com
> <yi...@hotmail.com>>
> > > Sent: Monday, May 11, 2020 4:52 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: RE: Modules in IE
> > >
> > > These lines in dialogPolyfill.as
> > >
> > > * <inject_html>
> > > * <script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262977136&sdata=67GEsWSZR7UoSl6774E53wr%2BdItmFimmWQ7Vzlt84Ow%3D&reserved=0
> > > "></script>
> > >
> > > get transpiled to
> > >
> > > document.head.innerHTML += '<script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262977136&sdata=67GEsWSZR7UoSl6774E53wr%2BdItmFimmWQ7Vzlt84Ow%3D&reserved=0
> > > "></script>'
> > >
> > > But that’s making IE11 fail in loading the module. It doesn’t
> matter
> > what
> > > the src is, IE will silently fail. For example, I’m getting the
> same
> > result
> > > if I replace the above with
> > >
> > > document.head.innerHTML += '<script></script>'
> > >
> > >
> > >
> > >
> > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > Sent: Sunday, May 10, 2020 7:35:55 PM
> > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > Does dialog-polyfill load correctly? Does it muck with the window
> > object?
> > >
> > > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> > >
> > > Test1.js isn’t different, but Test1_deps.js is.
> > >
> > > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > index 73eccbe..3e1a8a7 100644
> > > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > @@ -211,4 +211,4 @@
> > >
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > > ['org
> > > goog.addDependency('../../../XML.js', ['XML'], []);
> > >
> > > goog.require('Test1');
> > > -document.head.innerHTML += '<script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262977136&sdata=67GEsWSZR7UoSl6774E53wr%2BdItmFimmWQ7Vzlt84Ow%3D&reserved=0
> > > "></script<
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262977136&sdata=67GEsWSZR7UoSl6774E53wr%2BdItmFimmWQ7Vzlt84Ow%3D&reserved=0
> > > >>';document.head.innerHTM
> > > L += '<link rel="stylesheet" type="text/css" href="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262977136&sdata=bJoOT9dd%2Fqqcs5MziT4MtxL6DRqzBYHtXg%2FjapeNEbo%3D&reserved=0
> > > ">';
> > > +
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 10, 2020 6:39 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > Interesting. Just adding import shouldn't affect the output.
> > What is
> > > the difference between Test1.js with and without that import
> > statement?
> > >
> > > -Alex
> > >
> > > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> > wrote:
> > >
> > > I’ve narrowed it down to usage of mx.controls.Alert. Test
> > case is
> > > included in this issue [1].
> > >
> > > [1]
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262977136&sdata=v1SE2dxmwe54n6IWmLXgGSsxa1N5uRgmIEFZ90mAShE%3D&reserved=0
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, May 7, 2020 10:35 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > I think you can verify by debugging in some other browser
> > and see
> > > if breakpoints get set.
> > >
> > > A common “bug” in Flex modules was to reference and link
> the
> > > module class into the loading app. I have no idea what will happen
> > if you
> > > have such a situation in Royale. You can look at the loading app’s
> > > link-report to see if the module (Test1) is linked in the app and
> > probably
> > > see if Test1.js is in the output of the app if you start clean and
> > do not
> > > compile the module.
> > >
> > > HTH,
> > > -Alex
> > >
> > > From: Yishay Weiss <yi...@hotmail.com>
> > > Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > Date: Thursday, May 7, 2020 at 12:26 PM
> > > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > Subject: RE: Modules in IE
> > >
> > > url is
> > >
> > >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js
> >>>>>
> > >
> > > I don’t see errors other than
> > >
> > > SEC7113: CSS was ignored due to mime type mismatch
> > >
> > > But I don’t think that’s it.
> > >
> > > I put a debugger; statement on the first line of the src
> > which
> > > never kicks.
> > >
> > >
> > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there any
> errors
> > > loading and running it? Are the other Royale packages/classes in
> the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or something
> else
> > > creates a "window" property at the global window causing our
> package
> > lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <yishayjobs@hotmail.com
> >
> > wrote:
> > >
> > > In my example <script> element is there but it’s never
> > loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE and it
> > worked.
> > > Does it work for you?
> > > In the debugger, window.Module and window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache property.
> > > In the DOM Explorer, there should be tons of <script>
> > tags in
> > > the head. Near the end of the list should be the script for the
> .js
> > file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works without
> > errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Wednesday, May 6, 2020 7:58 PM
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there any
> errors
> > > loading and running it? Are the other Royale packages/classes in
> the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or something
> else
> > > creates a "window" property at the global window causing our
> package
> > lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <yishayjobs@hotmail.com
> >
> > wrote:
> > >
> > > In my example <script> element is there but it’s never
> > loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE and it
> > worked.
> > > Does it work for you?
> > > In the debugger, window.Module and window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache property.
> > > In the DOM Explorer, there should be tons of <script>
> > tags in
> > > the head. Near the end of the list should be the script for the
> .js
> > file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works without
> > errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 10, 2020 7:36 PM
> > > Subject: Re: Modules in IE
> > >
> > > Does dialog-polyfill load correctly? Does it muck with the window
> > object?
> > >
> > > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> > >
> > > Test1.js isn’t different, but Test1_deps.js is.
> > >
> > > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > index 73eccbe..3e1a8a7 100644
> > > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > @@ -211,4 +211,4 @@
> > >
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > > ['org
> > > goog.addDependency('../../../XML.js', ['XML'], []);
> > >
> > > goog.require('Test1');
> > > -document.head.innerHTML += '<script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262987138&sdata=TGGfD2mJ08463DmSxT3SC3tHTwUaYMlDvKdiq%2BN3cuo%3D&reserved=0
> > > "></script<
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262987138&sdata=TGGfD2mJ08463DmSxT3SC3tHTwUaYMlDvKdiq%2BN3cuo%3D&reserved=0
> > > >>';document.head.innerHTM
> > > L += '<link rel="stylesheet" type="text/css" href="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262987138&sdata=FAexclRes3j9Bq7f9EVF%2FMYmqotbhKvvwUFC7G0NOFQ%3D&reserved=0
> > > ">';
> > > +
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 10, 2020 6:39 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > Interesting. Just adding import shouldn't affect the output.
> > What is
> > > the difference between Test1.js with and without that import
> > statement?
> > >
> > > -Alex
> > >
> > > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> > wrote:
> > >
> > > I’ve narrowed it down to usage of mx.controls.Alert. Test
> > case is
> > > included in this issue [1].
> > >
> > > [1]
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262987138&sdata=KLBwD3V2m0dKjXz43iSF4O%2BRAFRCY7E4Y6H3eB6aumA%3D&reserved=0
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, May 7, 2020 10:35 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > I think you can verify by debugging in some other browser
> > and see
> > > if breakpoints get set.
> > >
> > > A common “bug” in Flex modules was to reference and link
> the
> > > module class into the loading app. I have no idea what will happen
> > if you
> > > have such a situation in Royale. You can look at the loading app’s
> > > link-report to see if the module (Test1) is linked in the app and
> > probably
> > > see if Test1.js is in the output of the app if you start clean and
> > do not
> > > compile the module.
> > >
> > > HTH,
> > > -Alex
> > >
> > > From: Yishay Weiss <yi...@hotmail.com>
> > > Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > Date: Thursday, May 7, 2020 at 12:26 PM
> > > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > Subject: RE: Modules in IE
> > >
> > > url is
> > >
> > >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js
> >>>>>
> > >
> > > I don’t see errors other than
> > >
> > > SEC7113: CSS was ignored due to mime type mismatch
> > >
> > > But I don’t think that’s it.
> > >
> > > I put a debugger; statement on the first line of the src
> > which
> > > never kicks.
> > >
> > >
> > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there any
> errors
> > > loading and running it? Are the other Royale packages/classes in
> the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or something
> else
> > > creates a "window" property at the global window causing our
> package
> > lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <yishayjobs@hotmail.com
> >
> > wrote:
> > >
> > > In my example <script> element is there but it’s never
> > loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE and it
> > worked.
> > > Does it work for you?
> > > In the debugger, window.Module and window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache property.
> > > In the DOM Explorer, there should be tons of <script>
> > tags in
> > > the head. Near the end of the list should be the script for the
> .js
> > file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works without
> > errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Wednesday, May 6, 2020 7:58 PM
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there any
> errors
> > > loading and running it? Are the other Royale packages/classes in
> the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or something
> else
> > > creates a "window" property at the global window causing our
> package
> > lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <yishayjobs@hotmail.com
> >
> > wrote:
> > >
> > > In my example <script> element is there but it’s never
> > loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE and it
> > worked.
> > > Does it work for you?
> > > In the debugger, window.Module and window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache property.
> > > In the DOM Explorer, there should be tons of <script>
> > tags in
> > > the head. Near the end of the list should be the script for the
> .js
> > file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works without
> > errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > --
> > Carlos Rovira
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262987138&sdata=akvITISjPogL8SiGthbXAdAqVAe8%2BX3XvO6nRUosNcI%3D&reserved=0
> >
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262987138&sdata=jcfN4%2FEFLRZ9QkTUqtkaRt7oo%2FQKK4Ak%2B3FfhjlFR3E%3D&reserved=0
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cc28000f713a44be2987408d7f8eab3c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637251559262987138&sdata=jcfN4%2FEFLRZ9QkTUqtkaRt7oo%2FQKK4Ak%2B3FfhjlFR3E%3D&reserved=0>*
>
>
>
Re: Modules in IE
Posted by Josh Tynjala <jo...@bowlerhat.dev>.
Any chance we can have inject_script work on the class instead of the
constructor? Ideally, inject_script would work on a function declared in a
package too.
package com.example {
/**
* <inject_script>
* //script here
* </inject_script>
*/
public function someFunction():void {}
}
--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>
On Fri, May 15, 2020 at 8:10 AM Yishay Weiss <yi...@hotmail.com> wrote:
> Thanks Piotr, I just merged.
>
>
>
> Carlos, sorry to create work for you but can you updated the
> documentation? [1]. Instead of
>
>
>
> * <inject_html>
>
> * <script src="//
> cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/highlight.min.js
> "></script>
>
> * <link rel="stylesheet" title="Atom One Dark" href="//
> cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/atom-one-dark.min.css
> ">
>
> * </inject_html>
>
>
>
> It should be
>
>
>
> * <inject_script>
>
> * var script = document.createElement("script");
>
> * script.setAttribute("src", "
> https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/highlight.min.js
> ");
>
> * document.head.appendChild(script);
>
> * var link = document.createElement("link");
>
> * link.setAttribute("rel", "stylesheet");
>
> * link.setAttribute("title", "Atom One Dark");
>
> * link.setAttribute("type", "text/css");
>
> * link.setAttribute("href", "
> https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/atom-one-dark.min.css
> ");
>
> * document.head.appendChild(link);
>
> * </inject_script>
>
>
>
> And
>
> “An inject_html directive declared in the constructor…”
>
> should be replaced with
>
> “An inject_script directive declared in the constructor…”.
>
>
>
> Thanks.
>
>
>
> [1]
> https://royale.apache.org/using-external-javascript-libraries-in-apache-royale/
>
>
>
>
>
>
>
>
>
> *From:* Piotr Zarzycki <pi...@gmail.com>
> *Sent:* Friday, May 15, 2020 5:41:07 PM
> *To:* Apache Royale Development <de...@royale.apache.org>
> *Subject:* Re: Modules in IE
>
>
>
> Yishay,
>
> I do not have any problems with that. I just missed point where you have
> said that is being removed. It's working so +1 from my sight on merge this.
>
> Thanks,
> Piotr
>
> pt., 15 maj 2020 o 16:35 Yishay Weiss <yi...@hotmail.com> napisał(a):
>
> >
> >
> > > Also, it is possible that inject_html is being overused (…) a static
> > initializer could bring in the code
> > Do we have an example of static initializers working in Royale? I tried
> > adding some code in curly brackets after the class declaration but I
> didn’t
> > see it transpiled.
> >
> > On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> >
> > Hi Carlos, thanks. The issue is with inject_html in modules on IE,
> > dialogPolyfill.js just happened to be the target src here. I’ve been
> > searching the net for solutions on IE and I think the trick is to append
> > elements instead of changing the inner html. I see two options of
> > transpiling <inject_html> that would work on IE:
> >
> >
> > 1. Parse the <inject_html> contents in the compiler and create js
> > that would work for IE. Difficult.
> > 2. Replace each line in <inject_html> with dummy elements and
> > change their outerHTML to match each line contents. This one looks
> easier,
> > but I seem to remember a thread where we were trying to eliminate use of
> > outerHTML.
> >
> >
> > Any thoughts are welcome.
> >
> > From: Carlos Rovira<mailto:carlosrovira@apache.org
> <ca...@apache.org>>
> > Sent: Monday, May 11, 2020 6:06 PM
> > To: Apache Royale Development<mailto:dev@royale.apache.org
> <de...@royale.apache.org>>
> > Subject: Re: Modules in IE
> >
> > Hi Yishay,
> >
> > talking without a huge analisys of the problem. I think Jewel Alert
> > works
> > ok in IE11 so that should mean dialogpolyfil is loading ok. if not
> the
> > case
> > something broke recently since I checked that in TDJ and other apps
> we
> > did.
> >
> > Anyway, the commit you state is just to give the support we needed. I
> > didn't tested in IE11, so don't know if we support it. Normally IE11
> > use to
> > require
> > some special way of writing the code for some particular things, so I
> > think
> > the way to solve this is:
> >
> > 1.- search in SOF or other sources how IE11 expect scripts to be
> added
> > dynamically
> > 2.- upgrade the compiler code to use that way with that
> considerations
> > to
> > make it IE11 compatible and check if that works for IE11 and rest of
> > browsers.
> >
> > sorry to not be able to say much more, but I'm these days with few
> time
> >
> > Thanks
> >
> >
> >
> > El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<
> > yishayjobs@hotmail.com>)
> > escribió:
> >
> > > Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in
> compiler
> > code
> > > doesn’t work for IE11. Any ideas on how to fix this?
> > >
> > > From: Yishay Weiss<mailto:yishayjobs@hotmail.com
> <yi...@hotmail.com>>
> > > Sent: Monday, May 11, 2020 4:52 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: RE: Modules in IE
> > >
> > > These lines in dialogPolyfill.as
> > >
> > > * <inject_html>
> > > * <script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > > "></script>
> > >
> > > get transpiled to
> > >
> > > document.head.innerHTML += '<script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > > "></script>'
> > >
> > > But that’s making IE11 fail in loading the module. It doesn’t
> matter
> > what
> > > the src is, IE will silently fail. For example, I’m getting the
> same
> > result
> > > if I replace the above with
> > >
> > > document.head.innerHTML += '<script></script>'
> > >
> > >
> > >
> > >
> > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > Sent: Sunday, May 10, 2020 7:35:55 PM
> > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > Does dialog-polyfill load correctly? Does it muck with the window
> > object?
> > >
> > > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> > >
> > > Test1.js isn’t different, but Test1_deps.js is.
> > >
> > > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > index 73eccbe..3e1a8a7 100644
> > > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > @@ -211,4 +211,4 @@
> > >
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > > ['org
> > > goog.addDependency('../../../XML.js', ['XML'], []);
> > >
> > > goog.require('Test1');
> > > -document.head.innerHTML += '<script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > > "></script<
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > > >>';document.head.innerHTM
> > > L += '<link rel="stylesheet" type="text/css" href="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=UhWgHnDOQVBBCGVW9RI3gwCcxHZcBcYjNu9bfmNEqbI%3D&reserved=0
> > > ">';
> > > +
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 10, 2020 6:39 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > Interesting. Just adding import shouldn't affect the output.
> > What is
> > > the difference between Test1.js with and without that import
> > statement?
> > >
> > > -Alex
> > >
> > > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> > wrote:
> > >
> > > I’ve narrowed it down to usage of mx.controls.Alert. Test
> > case is
> > > included in this issue [1].
> > >
> > > [1]
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=k5fxV4D7kTCIKILQxTYLYkIlTG29sSNaJiJ0gdnXkXM%3D&reserved=0
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, May 7, 2020 10:35 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > I think you can verify by debugging in some other browser
> > and see
> > > if breakpoints get set.
> > >
> > > A common “bug” in Flex modules was to reference and link
> the
> > > module class into the loading app. I have no idea what will happen
> > if you
> > > have such a situation in Royale. You can look at the loading app’s
> > > link-report to see if the module (Test1) is linked in the app and
> > probably
> > > see if Test1.js is in the output of the app if you start clean and
> > do not
> > > compile the module.
> > >
> > > HTH,
> > > -Alex
> > >
> > > From: Yishay Weiss <yi...@hotmail.com>
> > > Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > Date: Thursday, May 7, 2020 at 12:26 PM
> > > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > Subject: RE: Modules in IE
> > >
> > > url is
> > >
> > >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js
> >>>>>
> > >
> > > I don’t see errors other than
> > >
> > > SEC7113: CSS was ignored due to mime type mismatch
> > >
> > > But I don’t think that’s it.
> > >
> > > I put a debugger; statement on the first line of the src
> > which
> > > never kicks.
> > >
> > >
> > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there any
> errors
> > > loading and running it? Are the other Royale packages/classes in
> the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or something
> else
> > > creates a "window" property at the global window causing our
> package
> > lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <yishayjobs@hotmail.com
> >
> > wrote:
> > >
> > > In my example <script> element is there but it’s never
> > loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE and it
> > worked.
> > > Does it work for you?
> > > In the debugger, window.Module and window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache property.
> > > In the DOM Explorer, there should be tons of <script>
> > tags in
> > > the head. Near the end of the list should be the script for the
> .js
> > file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works without
> > errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Wednesday, May 6, 2020 7:58 PM
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there any
> errors
> > > loading and running it? Are the other Royale packages/classes in
> the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or something
> else
> > > creates a "window" property at the global window causing our
> package
> > lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <yishayjobs@hotmail.com
> >
> > wrote:
> > >
> > > In my example <script> element is there but it’s never
> > loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE and it
> > worked.
> > > Does it work for you?
> > > In the debugger, window.Module and window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache property.
> > > In the DOM Explorer, there should be tons of <script>
> > tags in
> > > the head. Near the end of the list should be the script for the
> .js
> > file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works without
> > errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 10, 2020 7:36 PM
> > > Subject: Re: Modules in IE
> > >
> > > Does dialog-polyfill load correctly? Does it muck with the window
> > object?
> > >
> > > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> > >
> > > Test1.js isn’t different, but Test1_deps.js is.
> > >
> > > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > index 73eccbe..3e1a8a7 100644
> > > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > @@ -211,4 +211,4 @@
> > >
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > > ['org
> > > goog.addDependency('../../../XML.js', ['XML'], []);
> > >
> > > goog.require('Test1');
> > > -document.head.innerHTML += '<script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > > "></script<
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > > >>';document.head.innerHTM
> > > L += '<link rel="stylesheet" type="text/css" href="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=90IzQjbCvQTqLKnJv4B0q0xP8L7tKRBcGZkeLzsv1hU%3D&reserved=0
> > > ">';
> > > +
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 10, 2020 6:39 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > Interesting. Just adding import shouldn't affect the output.
> > What is
> > > the difference between Test1.js with and without that import
> > statement?
> > >
> > > -Alex
> > >
> > > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> > wrote:
> > >
> > > I’ve narrowed it down to usage of mx.controls.Alert. Test
> > case is
> > > included in this issue [1].
> > >
> > > [1]
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=evkgF0%2BsdYs2Irz1Jigsgmn6Yq4IS7e4LLvGCJ4EReY%3D&reserved=0
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, May 7, 2020 10:35 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > I think you can verify by debugging in some other browser
> > and see
> > > if breakpoints get set.
> > >
> > > A common “bug” in Flex modules was to reference and link
> the
> > > module class into the loading app. I have no idea what will happen
> > if you
> > > have such a situation in Royale. You can look at the loading app’s
> > > link-report to see if the module (Test1) is linked in the app and
> > probably
> > > see if Test1.js is in the output of the app if you start clean and
> > do not
> > > compile the module.
> > >
> > > HTH,
> > > -Alex
> > >
> > > From: Yishay Weiss <yi...@hotmail.com>
> > > Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > Date: Thursday, May 7, 2020 at 12:26 PM
> > > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > Subject: RE: Modules in IE
> > >
> > > url is
> > >
> > >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js
> >>>>>
> > >
> > > I don’t see errors other than
> > >
> > > SEC7113: CSS was ignored due to mime type mismatch
> > >
> > > But I don’t think that’s it.
> > >
> > > I put a debugger; statement on the first line of the src
> > which
> > > never kicks.
> > >
> > >
> > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there any
> errors
> > > loading and running it? Are the other Royale packages/classes in
> the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or something
> else
> > > creates a "window" property at the global window causing our
> package
> > lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <yishayjobs@hotmail.com
> >
> > wrote:
> > >
> > > In my example <script> element is there but it’s never
> > loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE and it
> > worked.
> > > Does it work for you?
> > > In the debugger, window.Module and window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache property.
> > > In the DOM Explorer, there should be tons of <script>
> > tags in
> > > the head. Near the end of the list should be the script for the
> .js
> > file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works without
> > errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Wednesday, May 6, 2020 7:58 PM
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there any
> errors
> > > loading and running it? Are the other Royale packages/classes in
> the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or something
> else
> > > creates a "window" property at the global window causing our
> package
> > lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <yishayjobs@hotmail.com
> >
> > wrote:
> > >
> > > In my example <script> element is there but it’s never
> > loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE and it
> > worked.
> > > Does it work for you?
> > > In the debugger, window.Module and window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache property.
> > > In the DOM Explorer, there should be tons of <script>
> > tags in
> > > the head. Near the end of the list should be the script for the
> .js
> > file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works without
> > errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > --
> > Carlos Rovira
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=L0ya5B62P40fyCYZolQxaDCkYF0cbmuDHZhURTCXLPw%3D&reserved=0
> >
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
> *From: *Piotr Zarzycki <pi...@gmail.com>
> *Sent: *Friday, May 15, 2020 5:41 PM
> *To: *Apache Royale Development <de...@royale.apache.org>
> *Subject: *Re: Modules in IE
>
>
>
> Yishay,
>
> I do not have any problems with that. I just missed point where you have
> said that is being removed. It's working so +1 from my sight on merge this.
>
> Thanks,
> Piotr
>
> pt., 15 maj 2020 o 16:35 Yishay Weiss <yi...@hotmail.com> napisał(a):
>
> >
> >
> > > Also, it is possible that inject_html is being overused (…) a static
> > initializer could bring in the code
> > Do we have an example of static initializers working in Royale? I tried
> > adding some code in curly brackets after the class declaration but I
> didn’t
> > see it transpiled.
> >
> > On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> >
> > Hi Carlos, thanks. The issue is with inject_html in modules on IE,
> > dialogPolyfill.js just happened to be the target src here. I’ve been
> > searching the net for solutions on IE and I think the trick is to append
> > elements instead of changing the inner html. I see two options of
> > transpiling <inject_html> that would work on IE:
> >
> >
> > 1. Parse the <inject_html> contents in the compiler and create js
> > that would work for IE. Difficult.
> > 2. Replace each line in <inject_html> with dummy elements and
> > change their outerHTML to match each line contents. This one looks
> easier,
> > but I seem to remember a thread where we were trying to eliminate use of
> > outerHTML.
> >
> >
> > Any thoughts are welcome.
> >
> > From: Carlos Rovira<mailto:carlosrovira@apache.org
> <ca...@apache.org>>
> > Sent: Monday, May 11, 2020 6:06 PM
> > To: Apache Royale Development<mailto:dev@royale.apache.org
> <de...@royale.apache.org>>
> > Subject: Re: Modules in IE
> >
> > Hi Yishay,
> >
> > talking without a huge analisys of the problem. I think Jewel Alert
> > works
> > ok in IE11 so that should mean dialogpolyfil is loading ok. if not
> the
> > case
> > something broke recently since I checked that in TDJ and other apps
> we
> > did.
> >
> > Anyway, the commit you state is just to give the support we needed. I
> > didn't tested in IE11, so don't know if we support it. Normally IE11
> > use to
> > require
> > some special way of writing the code for some particular things, so I
> > think
> > the way to solve this is:
> >
> > 1.- search in SOF or other sources how IE11 expect scripts to be
> added
> > dynamically
> > 2.- upgrade the compiler code to use that way with that
> considerations
> > to
> > make it IE11 compatible and check if that works for IE11 and rest of
> > browsers.
> >
> > sorry to not be able to say much more, but I'm these days with few
> time
> >
> > Thanks
> >
> >
> >
> > El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<
> > yishayjobs@hotmail.com>)
> > escribió:
> >
> > > Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in
> compiler
> > code
> > > doesn’t work for IE11. Any ideas on how to fix this?
> > >
> > > From: Yishay Weiss<mailto:yishayjobs@hotmail.com
> <yi...@hotmail.com>>
> > > Sent: Monday, May 11, 2020 4:52 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: RE: Modules in IE
> > >
> > > These lines in dialogPolyfill.as
> > >
> > > * <inject_html>
> > > * <script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > > "></script>
> > >
> > > get transpiled to
> > >
> > > document.head.innerHTML += '<script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > > "></script>'
> > >
> > > But that’s making IE11 fail in loading the module. It doesn’t
> matter
> > what
> > > the src is, IE will silently fail. For example, I’m getting the
> same
> > result
> > > if I replace the above with
> > >
> > > document.head.innerHTML += '<script></script>'
> > >
> > >
> > >
> > >
> > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > Sent: Sunday, May 10, 2020 7:35:55 PM
> > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > Does dialog-polyfill load correctly? Does it muck with the window
> > object?
> > >
> > > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> > >
> > > Test1.js isn’t different, but Test1_deps.js is.
> > >
> > > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > index 73eccbe..3e1a8a7 100644
> > > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > @@ -211,4 +211,4 @@
> > >
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > > ['org
> > > goog.addDependency('../../../XML.js', ['XML'], []);
> > >
> > > goog.require('Test1');
> > > -document.head.innerHTML += '<script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > > "></script<
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > > >>';document.head.innerHTM
> > > L += '<link rel="stylesheet" type="text/css" href="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=UhWgHnDOQVBBCGVW9RI3gwCcxHZcBcYjNu9bfmNEqbI%3D&reserved=0
> > > ">';
> > > +
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 10, 2020 6:39 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > Interesting. Just adding import shouldn't affect the output.
> > What is
> > > the difference between Test1.js with and without that import
> > statement?
> > >
> > > -Alex
> > >
> > > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> > wrote:
> > >
> > > I’ve narrowed it down to usage of mx.controls.Alert. Test
> > case is
> > > included in this issue [1].
> > >
> > > [1]
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=k5fxV4D7kTCIKILQxTYLYkIlTG29sSNaJiJ0gdnXkXM%3D&reserved=0
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, May 7, 2020 10:35 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > I think you can verify by debugging in some other browser
> > and see
> > > if breakpoints get set.
> > >
> > > A common “bug” in Flex modules was to reference and link
> the
> > > module class into the loading app. I have no idea what will happen
> > if you
> > > have such a situation in Royale. You can look at the loading app’s
> > > link-report to see if the module (Test1) is linked in the app and
> > probably
> > > see if Test1.js is in the output of the app if you start clean and
> > do not
> > > compile the module.
> > >
> > > HTH,
> > > -Alex
> > >
> > > From: Yishay Weiss <yi...@hotmail.com>
> > > Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > Date: Thursday, May 7, 2020 at 12:26 PM
> > > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > Subject: RE: Modules in IE
> > >
> > > url is
> > >
> > >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js
> >>>>>
> > >
> > > I don’t see errors other than
> > >
> > > SEC7113: CSS was ignored due to mime type mismatch
> > >
> > > But I don’t think that’s it.
> > >
> > > I put a debugger; statement on the first line of the src
> > which
> > > never kicks.
> > >
> > >
> > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there any
> errors
> > > loading and running it? Are the other Royale packages/classes in
> the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or something
> else
> > > creates a "window" property at the global window causing our
> package
> > lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <yishayjobs@hotmail.com
> >
> > wrote:
> > >
> > > In my example <script> element is there but it’s never
> > loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE and it
> > worked.
> > > Does it work for you?
> > > In the debugger, window.Module and window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache property.
> > > In the DOM Explorer, there should be tons of <script>
> > tags in
> > > the head. Near the end of the list should be the script for the
> .js
> > file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works without
> > errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Wednesday, May 6, 2020 7:58 PM
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there any
> errors
> > > loading and running it? Are the other Royale packages/classes in
> the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or something
> else
> > > creates a "window" property at the global window causing our
> package
> > lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <yishayjobs@hotmail.com
> >
> > wrote:
> > >
> > > In my example <script> element is there but it’s never
> > loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE and it
> > worked.
> > > Does it work for you?
> > > In the debugger, window.Module and window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache property.
> > > In the DOM Explorer, there should be tons of <script>
> > tags in
> > > the head. Near the end of the list should be the script for the
> .js
> > file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works without
> > errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 10, 2020 7:36 PM
> > > Subject: Re: Modules in IE
> > >
> > > Does dialog-polyfill load correctly? Does it muck with the window
> > object?
> > >
> > > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> > >
> > > Test1.js isn’t different, but Test1_deps.js is.
> > >
> > > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > index 73eccbe..3e1a8a7 100644
> > > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > > @@ -211,4 +211,4 @@
> > >
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > > ['org
> > > goog.addDependency('../../../XML.js', ['XML'], []);
> > >
> > > goog.require('Test1');
> > > -document.head.innerHTML += '<script src="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > > "></script<
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > > >>';document.head.innerHTM
> > > L += '<link rel="stylesheet" type="text/css" href="
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=90IzQjbCvQTqLKnJv4B0q0xP8L7tKRBcGZkeLzsv1hU%3D&reserved=0
> > > ">';
> > > +
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 10, 2020 6:39 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > Interesting. Just adding import shouldn't affect the output.
> > What is
> > > the difference between Test1.js with and without that import
> > statement?
> > >
> > > -Alex
> > >
> > > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> > wrote:
> > >
> > > I’ve narrowed it down to usage of mx.controls.Alert. Test
> > case is
> > > included in this issue [1].
> > >
> > > [1]
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=evkgF0%2BsdYs2Irz1Jigsgmn6Yq4IS7e4LLvGCJ4EReY%3D&reserved=0
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, May 7, 2020 10:35 PM
> > > To: dev@royale.apache.org<ma...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > I think you can verify by debugging in some other browser
> > and see
> > > if breakpoints get set.
> > >
> > > A common “bug” in Flex modules was to reference and link
> the
> > > module class into the loading app. I have no idea what will happen
> > if you
> > > have such a situation in Royale. You can look at the loading app’s
> > > link-report to see if the module (Test1) is linked in the app and
> > probably
> > > see if Test1.js is in the output of the app if you start clean and
> > do not
> > > compile the module.
> > >
> > > HTH,
> > > -Alex
> > >
> > > From: Yishay Weiss <yi...@hotmail.com>
> > > Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > Date: Thursday, May 7, 2020 at 12:26 PM
> > > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > > Subject: RE: Modules in IE
> > >
> > > url is
> > >
> > >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js
> >>>>>
> > >
> > > I don’t see errors other than
> > >
> > > SEC7113: CSS was ignored due to mime type mismatch
> > >
> > > But I don’t think that’s it.
> > >
> > > I put a debugger; statement on the first line of the src
> > which
> > > never kicks.
> > >
> > >
> > > From: Alex Harui <ah...@adobe.com.INVALID>
> > > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > > To: dev@royale.apache.org <de...@royale.apache.org>
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there any
> errors
> > > loading and running it? Are the other Royale packages/classes in
> the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or something
> else
> > > creates a "window" property at the global window causing our
> package
> > lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <yishayjobs@hotmail.com
> >
> > wrote:
> > >
> > > In my example <script> element is there but it’s never
> > loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE and it
> > worked.
> > > Does it work for you?
> > > In the debugger, window.Module and window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache property.
> > > In the DOM Explorer, there should be tons of <script>
> > tags in
> > > the head. Near the end of the list should be the script for the
> .js
> > file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works without
> > errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Wednesday, May 6, 2020 7:58 PM
> > > Subject: Re: Modules in IE
> > >
> > > What is the src (url) for that script? Were there any
> errors
> > > loading and running it? Are the other Royale packages/classes in
> the
> > > "window" object?
> > >
> > > One scenario I thought of is that some bug or something
> else
> > > creates a "window" property at the global window causing our
> package
> > lookup
> > > to be off.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 5/6/20, 8:47 AM, "Yishay Weiss" <yishayjobs@hotmail.com
> >
> > wrote:
> > >
> > > In my example <script> element is there but it’s never
> > loaded
> > > on IE. I can confirm ModuleExamle works.
> > >
> > > From: Alex Harui<mailto:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Sunday, May 3, 2020 9:31 AM
> > > To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> > > Subject: Re: Modules in IE
> > >
> > > I just ran examples/royale/ModuleExample in IE and it
> > worked.
> > > Does it work for you?
> > > In the debugger, window.Module and window.MainApp
> > resolve to
> > > functions. window.org is an object with an apache property.
> > > In the DOM Explorer, there should be tons of <script>
> > tags in
> > > the head. Near the end of the list should be the script for the
> .js
> > file
> > > for the module.
> > > Do you see any exceptions? ModuleExample works without
> > errors.
> > >
> > > -Alex
> > >
> > > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> > yishayjobs@hotmail.com>
> > > wrote:
> > >
> > > 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:aharui@adobe.com.INVALID
> <ah...@adobe.com.INVALID>>
> > > Sent: Thursday, April 30, 2020 6:29 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org>
> > > 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" <
> > > yishayjobs@hotmail.com> 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:
> aharui@adobe.com.INVALID
> > >
> > > Sent: Thursday, April 30, 2020 12:00 AM
> > > To: dev@royale.apache.org<mailto:
> > dev@royale.apache.org
> > > >
> > > 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" <
> > > yishayjobs@hotmail.com> 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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > --
> > Carlos Rovira
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=L0ya5B62P40fyCYZolQxaDCkYF0cbmuDHZhURTCXLPw%3D&reserved=0
> >
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
>
>
RE: Modules in IE
Posted by Yishay Weiss <yi...@hotmail.com>.
Thanks Piotr, I just merged.
Carlos, sorry to create work for you but can you updated the documentation? [1]. Instead of
* <inject_html>
* <script src="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/highlight.min.js"></script>
* <link rel="stylesheet" title="Atom One Dark" href="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/atom-one-dark.min.css">
* </inject_html>
It should be
* <inject_script>
* var script = document.createElement("script");
* script.setAttribute("src", "https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/highlight.min.js");
* document.head.appendChild(script);
* var link = document.createElement("link");
* link.setAttribute("rel", "stylesheet");
* link.setAttribute("title", "Atom One Dark");
* link.setAttribute("type", "text/css");
* link.setAttribute("href", "https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/atom-one-dark.min.css");
* document.head.appendChild(link);
* </inject_script>
And
“An inject_html directive declared in the constructor…”
should be replaced with
“An inject_script directive declared in the constructor…”.
Thanks.
[1] https://royale.apache.org/using-external-javascript-libraries-in-apache-royale/
From: Piotr Zarzycki <pi...@gmail.com>
Sent: Friday, May 15, 2020 5:41:07 PM
To: Apache Royale Development <de...@royale.apache.org>
Subject: Re: Modules in IE
Yishay,
I do not have any problems with that. I just missed point where you have
said that is being removed. It's working so +1 from my sight on merge this.
Thanks,
Piotr
pt., 15 maj 2020 o 16:35 Yishay Weiss <yi...@hotmail.com> napisał(a):
>
>
> > Also, it is possible that inject_html is being overused (…) a static
> initializer could bring in the code
> Do we have an example of static initializers working in Royale? I tried
> adding some code in curly brackets after the class declaration but I didn’t
> see it transpiled.
>
> On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Hi Carlos, thanks. The issue is with inject_html in modules on IE,
> dialogPolyfill.js just happened to be the target src here. I’ve been
> searching the net for solutions on IE and I think the trick is to append
> elements instead of changing the inner html. I see two options of
> transpiling <inject_html> that would work on IE:
>
>
> 1. Parse the <inject_html> contents in the compiler and create js
> that would work for IE. Difficult.
> 2. Replace each line in <inject_html> with dummy elements and
> change their outerHTML to match each line contents. This one looks easier,
> but I seem to remember a thread where we were trying to eliminate use of
> outerHTML.
>
>
> Any thoughts are welcome.
>
> From: Carlos Rovira<ma...@apache.org>
> Sent: Monday, May 11, 2020 6:06 PM
> To: Apache Royale Development<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Hi Yishay,
>
> talking without a huge analisys of the problem. I think Jewel Alert
> works
> ok in IE11 so that should mean dialogpolyfil is loading ok. if not the
> case
> something broke recently since I checked that in TDJ and other apps we
> did.
>
> Anyway, the commit you state is just to give the support we needed. I
> didn't tested in IE11, so don't know if we support it. Normally IE11
> use to
> require
> some special way of writing the code for some particular things, so I
> think
> the way to solve this is:
>
> 1.- search in SOF or other sources how IE11 expect scripts to be added
> dynamically
> 2.- upgrade the compiler code to use that way with that considerations
> to
> make it IE11 compatible and check if that works for IE11 and rest of
> browsers.
>
> sorry to not be able to say much more, but I'm these days with few time
>
> Thanks
>
>
>
> El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<
> yishayjobs@hotmail.com>)
> escribió:
>
> > Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in compiler
> code
> > doesn’t work for IE11. Any ideas on how to fix this?
> >
> > From: Yishay Weiss<ma...@hotmail.com>
> > Sent: Monday, May 11, 2020 4:52 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > These lines in dialogPolyfill.as
> >
> > * <inject_html>
> > * <script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > "></script>
> >
> > get transpiled to
> >
> > document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > "></script>'
> >
> > But that’s making IE11 fail in loading the module. It doesn’t matter
> what
> > the src is, IE will silently fail. For example, I’m getting the same
> result
> > if I replace the above with
> >
> > document.head.innerHTML += '<script></script>'
> >
> >
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 7:35:55 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Does dialog-polyfill load correctly? Does it muck with the window
> object?
> >
> > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> >
> > Test1.js isn’t different, but Test1_deps.js is.
> >
> > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > index 73eccbe..3e1a8a7 100644
> > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > @@ -211,4 +211,4 @@
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > ['org
> > goog.addDependency('../../../XML.js', ['XML'], []);
> >
> > goog.require('Test1');
> > -document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > "></script<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > >>';document.head.innerHTM
> > L += '<link rel="stylesheet" type="text/css" href="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=UhWgHnDOQVBBCGVW9RI3gwCcxHZcBcYjNu9bfmNEqbI%3D&reserved=0
> > ">';
> > +
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 6:39 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Interesting. Just adding import shouldn't affect the output.
> What is
> > the difference between Test1.js with and without that import
> statement?
> >
> > -Alex
> >
> > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > I’ve narrowed it down to usage of mx.controls.Alert. Test
> case is
> > included in this issue [1].
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=k5fxV4D7kTCIKILQxTYLYkIlTG29sSNaJiJ0gdnXkXM%3D&reserved=0
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Thursday, May 7, 2020 10:35 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I think you can verify by debugging in some other browser
> and see
> > if breakpoints get set.
> >
> > A common “bug” in Flex modules was to reference and link the
> > module class into the loading app. I have no idea what will happen
> if you
> > have such a situation in Royale. You can look at the loading app’s
> > link-report to see if the module (Test1) is linked in the app and
> probably
> > see if Test1.js is in the output of the app if you start clean and
> do not
> > compile the module.
> >
> > HTH,
> > -Alex
> >
> > From: Yishay Weiss <yi...@hotmail.com>
> > Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Date: Thursday, May 7, 2020 at 12:26 PM
> > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > url is
> >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>>>>>>
> >
> > I don’t see errors other than
> >
> > SEC7113: CSS was ignored due to mime type mismatch
> >
> > But I don’t think that’s it.
> >
> > I put a debugger; statement on the first line of the src
> which
> > never kicks.
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any errors
> > loading and running it? Are the other Royale packages/classes in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something else
> > creates a "window" property at the global window causing our package
> lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > In my example <script> element is there but it’s never
> loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and it
> worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of <script>
> tags in
> > the head. Near the end of the list should be the script for the .js
> file
> > for the module.
> > Do you see any exceptions? ModuleExample works without
> errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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<ma...@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58 PM
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any errors
> > loading and running it? Are the other Royale packages/classes in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something else
> > creates a "window" property at the global window causing our package
> lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > In my example <script> element is there but it’s never
> loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and it
> worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of <script>
> tags in
> > the head. Near the end of the list should be the script for the .js
> file
> > for the module.
> > Do you see any exceptions? ModuleExample works without
> errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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<ma...@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 7:36 PM
> > Subject: Re: Modules in IE
> >
> > Does dialog-polyfill load correctly? Does it muck with the window
> object?
> >
> > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> >
> > Test1.js isn’t different, but Test1_deps.js is.
> >
> > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > index 73eccbe..3e1a8a7 100644
> > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > @@ -211,4 +211,4 @@
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > ['org
> > goog.addDependency('../../../XML.js', ['XML'], []);
> >
> > goog.require('Test1');
> > -document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > "></script<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > >>';document.head.innerHTM
> > L += '<link rel="stylesheet" type="text/css" href="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=90IzQjbCvQTqLKnJv4B0q0xP8L7tKRBcGZkeLzsv1hU%3D&reserved=0
> > ">';
> > +
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 6:39 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Interesting. Just adding import shouldn't affect the output.
> What is
> > the difference between Test1.js with and without that import
> statement?
> >
> > -Alex
> >
> > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > I’ve narrowed it down to usage of mx.controls.Alert. Test
> case is
> > included in this issue [1].
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=evkgF0%2BsdYs2Irz1Jigsgmn6Yq4IS7e4LLvGCJ4EReY%3D&reserved=0
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Thursday, May 7, 2020 10:35 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I think you can verify by debugging in some other browser
> and see
> > if breakpoints get set.
> >
> > A common “bug” in Flex modules was to reference and link the
> > module class into the loading app. I have no idea what will happen
> if you
> > have such a situation in Royale. You can look at the loading app’s
> > link-report to see if the module (Test1) is linked in the app and
> probably
> > see if Test1.js is in the output of the app if you start clean and
> do not
> > compile the module.
> >
> > HTH,
> > -Alex
> >
> > From: Yishay Weiss <yi...@hotmail.com>
> > Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Date: Thursday, May 7, 2020 at 12:26 PM
> > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > url is
> >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>>>>>>
> >
> > I don’t see errors other than
> >
> > SEC7113: CSS was ignored due to mime type mismatch
> >
> > But I don’t think that’s it.
> >
> > I put a debugger; statement on the first line of the src
> which
> > never kicks.
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any errors
> > loading and running it? Are the other Royale packages/classes in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something else
> > creates a "window" property at the global window causing our package
> lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > In my example <script> element is there but it’s never
> loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and it
> worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of <script>
> tags in
> > the head. Near the end of the list should be the script for the .js
> file
> > for the module.
> > Do you see any exceptions? ModuleExample works without
> errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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<ma...@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58 PM
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any errors
> > loading and running it? Are the other Royale packages/classes in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something else
> > creates a "window" property at the global window causing our package
> lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > In my example <script> element is there but it’s never
> loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and it
> worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of <script>
> tags in
> > the head. Near the end of the list should be the script for the .js
> file
> > for the module.
> > Do you see any exceptions? ModuleExample works without
> errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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<ma...@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=L0ya5B62P40fyCYZolQxaDCkYF0cbmuDHZhURTCXLPw%3D&reserved=0
>
>
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
From: Piotr Zarzycki<ma...@gmail.com>
Sent: Friday, May 15, 2020 5:41 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: Modules in IE
Yishay,
I do not have any problems with that. I just missed point where you have
said that is being removed. It's working so +1 from my sight on merge this.
Thanks,
Piotr
pt., 15 maj 2020 o 16:35 Yishay Weiss <yi...@hotmail.com> napisał(a):
>
>
> > Also, it is possible that inject_html is being overused (…) a static
> initializer could bring in the code
> Do we have an example of static initializers working in Royale? I tried
> adding some code in curly brackets after the class declaration but I didn’t
> see it transpiled.
>
> On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Hi Carlos, thanks. The issue is with inject_html in modules on IE,
> dialogPolyfill.js just happened to be the target src here. I’ve been
> searching the net for solutions on IE and I think the trick is to append
> elements instead of changing the inner html. I see two options of
> transpiling <inject_html> that would work on IE:
>
>
> 1. Parse the <inject_html> contents in the compiler and create js
> that would work for IE. Difficult.
> 2. Replace each line in <inject_html> with dummy elements and
> change their outerHTML to match each line contents. This one looks easier,
> but I seem to remember a thread where we were trying to eliminate use of
> outerHTML.
>
>
> Any thoughts are welcome.
>
> From: Carlos Rovira<ma...@apache.org>
> Sent: Monday, May 11, 2020 6:06 PM
> To: Apache Royale Development<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Hi Yishay,
>
> talking without a huge analisys of the problem. I think Jewel Alert
> works
> ok in IE11 so that should mean dialogpolyfil is loading ok. if not the
> case
> something broke recently since I checked that in TDJ and other apps we
> did.
>
> Anyway, the commit you state is just to give the support we needed. I
> didn't tested in IE11, so don't know if we support it. Normally IE11
> use to
> require
> some special way of writing the code for some particular things, so I
> think
> the way to solve this is:
>
> 1.- search in SOF or other sources how IE11 expect scripts to be added
> dynamically
> 2.- upgrade the compiler code to use that way with that considerations
> to
> make it IE11 compatible and check if that works for IE11 and rest of
> browsers.
>
> sorry to not be able to say much more, but I'm these days with few time
>
> Thanks
>
>
>
> El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<
> yishayjobs@hotmail.com>)
> escribió:
>
> > Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in compiler
> code
> > doesn’t work for IE11. Any ideas on how to fix this?
> >
> > From: Yishay Weiss<ma...@hotmail.com>
> > Sent: Monday, May 11, 2020 4:52 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > These lines in dialogPolyfill.as
> >
> > * <inject_html>
> > * <script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > "></script>
> >
> > get transpiled to
> >
> > document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > "></script>'
> >
> > But that’s making IE11 fail in loading the module. It doesn’t matter
> what
> > the src is, IE will silently fail. For example, I’m getting the same
> result
> > if I replace the above with
> >
> > document.head.innerHTML += '<script></script>'
> >
> >
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 7:35:55 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Does dialog-polyfill load correctly? Does it muck with the window
> object?
> >
> > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> >
> > Test1.js isn’t different, but Test1_deps.js is.
> >
> > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > index 73eccbe..3e1a8a7 100644
> > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > @@ -211,4 +211,4 @@
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > ['org
> > goog.addDependency('../../../XML.js', ['XML'], []);
> >
> > goog.require('Test1');
> > -document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > "></script<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > >>';document.head.innerHTM
> > L += '<link rel="stylesheet" type="text/css" href="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=UhWgHnDOQVBBCGVW9RI3gwCcxHZcBcYjNu9bfmNEqbI%3D&reserved=0
> > ">';
> > +
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 6:39 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Interesting. Just adding import shouldn't affect the output.
> What is
> > the difference between Test1.js with and without that import
> statement?
> >
> > -Alex
> >
> > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > I’ve narrowed it down to usage of mx.controls.Alert. Test
> case is
> > included in this issue [1].
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=k5fxV4D7kTCIKILQxTYLYkIlTG29sSNaJiJ0gdnXkXM%3D&reserved=0
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Thursday, May 7, 2020 10:35 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I think you can verify by debugging in some other browser
> and see
> > if breakpoints get set.
> >
> > A common “bug” in Flex modules was to reference and link the
> > module class into the loading app. I have no idea what will happen
> if you
> > have such a situation in Royale. You can look at the loading app’s
> > link-report to see if the module (Test1) is linked in the app and
> probably
> > see if Test1.js is in the output of the app if you start clean and
> do not
> > compile the module.
> >
> > HTH,
> > -Alex
> >
> > From: Yishay Weiss <yi...@hotmail.com>
> > Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Date: Thursday, May 7, 2020 at 12:26 PM
> > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > url is
> >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>>>>>>
> >
> > I don’t see errors other than
> >
> > SEC7113: CSS was ignored due to mime type mismatch
> >
> > But I don’t think that’s it.
> >
> > I put a debugger; statement on the first line of the src
> which
> > never kicks.
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any errors
> > loading and running it? Are the other Royale packages/classes in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something else
> > creates a "window" property at the global window causing our package
> lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > In my example <script> element is there but it’s never
> loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and it
> worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of <script>
> tags in
> > the head. Near the end of the list should be the script for the .js
> file
> > for the module.
> > Do you see any exceptions? ModuleExample works without
> errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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<ma...@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58 PM
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any errors
> > loading and running it? Are the other Royale packages/classes in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something else
> > creates a "window" property at the global window causing our package
> lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > In my example <script> element is there but it’s never
> loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and it
> worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of <script>
> tags in
> > the head. Near the end of the list should be the script for the .js
> file
> > for the module.
> > Do you see any exceptions? ModuleExample works without
> errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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<ma...@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 7:36 PM
> > Subject: Re: Modules in IE
> >
> > Does dialog-polyfill load correctly? Does it muck with the window
> object?
> >
> > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> >
> > Test1.js isn’t different, but Test1_deps.js is.
> >
> > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > index 73eccbe..3e1a8a7 100644
> > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > @@ -211,4 +211,4 @@
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > ['org
> > goog.addDependency('../../../XML.js', ['XML'], []);
> >
> > goog.require('Test1');
> > -document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > "></script<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > >>';document.head.innerHTM
> > L += '<link rel="stylesheet" type="text/css" href="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=90IzQjbCvQTqLKnJv4B0q0xP8L7tKRBcGZkeLzsv1hU%3D&reserved=0
> > ">';
> > +
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 6:39 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Interesting. Just adding import shouldn't affect the output.
> What is
> > the difference between Test1.js with and without that import
> statement?
> >
> > -Alex
> >
> > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > I’ve narrowed it down to usage of mx.controls.Alert. Test
> case is
> > included in this issue [1].
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=evkgF0%2BsdYs2Irz1Jigsgmn6Yq4IS7e4LLvGCJ4EReY%3D&reserved=0
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Thursday, May 7, 2020 10:35 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I think you can verify by debugging in some other browser
> and see
> > if breakpoints get set.
> >
> > A common “bug” in Flex modules was to reference and link the
> > module class into the loading app. I have no idea what will happen
> if you
> > have such a situation in Royale. You can look at the loading app’s
> > link-report to see if the module (Test1) is linked in the app and
> probably
> > see if Test1.js is in the output of the app if you start clean and
> do not
> > compile the module.
> >
> > HTH,
> > -Alex
> >
> > From: Yishay Weiss <yi...@hotmail.com>
> > Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Date: Thursday, May 7, 2020 at 12:26 PM
> > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > url is
> >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/>>>>>>
> >
> > I don’t see errors other than
> >
> > SEC7113: CSS was ignored due to mime type mismatch
> >
> > But I don’t think that’s it.
> >
> > I put a debugger; statement on the first line of the src
> which
> > never kicks.
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any errors
> > loading and running it? Are the other Royale packages/classes in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something else
> > creates a "window" property at the global window causing our package
> lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > In my example <script> element is there but it’s never
> loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and it
> worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of <script>
> tags in
> > the head. Near the end of the list should be the script for the .js
> file
> > for the module.
> > Do you see any exceptions? ModuleExample works without
> errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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<ma...@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58 PM
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any errors
> > loading and running it? Are the other Royale packages/classes in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something else
> > creates a "window" property at the global window causing our package
> lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > In my example <script> element is there but it’s never
> loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and it
> worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of <script>
> tags in
> > the head. Near the end of the list should be the script for the .js
> file
> > for the module.
> > Do you see any exceptions? ModuleExample works without
> errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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<ma...@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=L0ya5B62P40fyCYZolQxaDCkYF0cbmuDHZhURTCXLPw%3D&reserved=0
>
>
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Modules in IE
Posted by Piotr Zarzycki <pi...@gmail.com>.
Yishay,
I do not have any problems with that. I just missed point where you have
said that is being removed. It's working so +1 from my sight on merge this.
Thanks,
Piotr
pt., 15 maj 2020 o 16:35 Yishay Weiss <yi...@hotmail.com> napisał(a):
>
>
> > Also, it is possible that inject_html is being overused (…) a static
> initializer could bring in the code
> Do we have an example of static initializers working in Royale? I tried
> adding some code in curly brackets after the class declaration but I didn’t
> see it transpiled.
>
> On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Hi Carlos, thanks. The issue is with inject_html in modules on IE,
> dialogPolyfill.js just happened to be the target src here. I’ve been
> searching the net for solutions on IE and I think the trick is to append
> elements instead of changing the inner html. I see two options of
> transpiling <inject_html> that would work on IE:
>
>
> 1. Parse the <inject_html> contents in the compiler and create js
> that would work for IE. Difficult.
> 2. Replace each line in <inject_html> with dummy elements and
> change their outerHTML to match each line contents. This one looks easier,
> but I seem to remember a thread where we were trying to eliminate use of
> outerHTML.
>
>
> Any thoughts are welcome.
>
> From: Carlos Rovira<ma...@apache.org>
> Sent: Monday, May 11, 2020 6:06 PM
> To: Apache Royale Development<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Hi Yishay,
>
> talking without a huge analisys of the problem. I think Jewel Alert
> works
> ok in IE11 so that should mean dialogpolyfil is loading ok. if not the
> case
> something broke recently since I checked that in TDJ and other apps we
> did.
>
> Anyway, the commit you state is just to give the support we needed. I
> didn't tested in IE11, so don't know if we support it. Normally IE11
> use to
> require
> some special way of writing the code for some particular things, so I
> think
> the way to solve this is:
>
> 1.- search in SOF or other sources how IE11 expect scripts to be added
> dynamically
> 2.- upgrade the compiler code to use that way with that considerations
> to
> make it IE11 compatible and check if that works for IE11 and rest of
> browsers.
>
> sorry to not be able to say much more, but I'm these days with few time
>
> Thanks
>
>
>
> El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<
> yishayjobs@hotmail.com>)
> escribió:
>
> > Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in compiler
> code
> > doesn’t work for IE11. Any ideas on how to fix this?
> >
> > From: Yishay Weiss<ma...@hotmail.com>
> > Sent: Monday, May 11, 2020 4:52 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > These lines in dialogPolyfill.as
> >
> > * <inject_html>
> > * <script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > "></script>
> >
> > get transpiled to
> >
> > document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > "></script>'
> >
> > But that’s making IE11 fail in loading the module. It doesn’t matter
> what
> > the src is, IE will silently fail. For example, I’m getting the same
> result
> > if I replace the above with
> >
> > document.head.innerHTML += '<script></script>'
> >
> >
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 7:35:55 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Does dialog-polyfill load correctly? Does it muck with the window
> object?
> >
> > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> >
> > Test1.js isn’t different, but Test1_deps.js is.
> >
> > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > index 73eccbe..3e1a8a7 100644
> > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > @@ -211,4 +211,4 @@
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > ['org
> > goog.addDependency('../../../XML.js', ['XML'], []);
> >
> > goog.require('Test1');
> > -document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > "></script<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > >>';document.head.innerHTM
> > L += '<link rel="stylesheet" type="text/css" href="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=UhWgHnDOQVBBCGVW9RI3gwCcxHZcBcYjNu9bfmNEqbI%3D&reserved=0
> > ">';
> > +
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 6:39 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Interesting. Just adding import shouldn't affect the output.
> What is
> > the difference between Test1.js with and without that import
> statement?
> >
> > -Alex
> >
> > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > I’ve narrowed it down to usage of mx.controls.Alert. Test
> case is
> > included in this issue [1].
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=k5fxV4D7kTCIKILQxTYLYkIlTG29sSNaJiJ0gdnXkXM%3D&reserved=0
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Thursday, May 7, 2020 10:35 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I think you can verify by debugging in some other browser
> and see
> > if breakpoints get set.
> >
> > A common “bug” in Flex modules was to reference and link the
> > module class into the loading app. I have no idea what will happen
> if you
> > have such a situation in Royale. You can look at the loading app’s
> > link-report to see if the module (Test1) is linked in the app and
> probably
> > see if Test1.js is in the output of the app if you start clean and
> do not
> > compile the module.
> >
> > HTH,
> > -Alex
> >
> > From: Yishay Weiss <yi...@hotmail.com>
> > Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Date: Thursday, May 7, 2020 at 12:26 PM
> > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > url is
> >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>>
> >
> > I don’t see errors other than
> >
> > SEC7113: CSS was ignored due to mime type mismatch
> >
> > But I don’t think that’s it.
> >
> > I put a debugger; statement on the first line of the src
> which
> > never kicks.
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any errors
> > loading and running it? Are the other Royale packages/classes in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something else
> > creates a "window" property at the global window causing our package
> lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > In my example <script> element is there but it’s never
> loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and it
> worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of <script>
> tags in
> > the head. Near the end of the list should be the script for the .js
> file
> > for the module.
> > Do you see any exceptions? ModuleExample works without
> errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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<ma...@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58 PM
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any errors
> > loading and running it? Are the other Royale packages/classes in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something else
> > creates a "window" property at the global window causing our package
> lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > In my example <script> element is there but it’s never
> loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and it
> worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of <script>
> tags in
> > the head. Near the end of the list should be the script for the .js
> file
> > for the module.
> > Do you see any exceptions? ModuleExample works without
> errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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<ma...@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 7:36 PM
> > Subject: Re: Modules in IE
> >
> > Does dialog-polyfill load correctly? Does it muck with the window
> object?
> >
> > On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
> >
> > Test1.js isn’t different, but Test1_deps.js is.
> >
> > diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > index 73eccbe..3e1a8a7 100644
> > --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> > +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> > @@ -211,4 +211,4 @@
> >
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> > ['org
> > goog.addDependency('../../../XML.js', ['XML'], []);
> >
> > goog.require('Test1');
> > -document.head.innerHTML += '<script src="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > "></script<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> > >>';document.head.innerHTM
> > L += '<link rel="stylesheet" type="text/css" href="
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=90IzQjbCvQTqLKnJv4B0q0xP8L7tKRBcGZkeLzsv1hU%3D&reserved=0
> > ">';
> > +
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 10, 2020 6:39 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > Interesting. Just adding import shouldn't affect the output.
> What is
> > the difference between Test1.js with and without that import
> statement?
> >
> > -Alex
> >
> > On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > I’ve narrowed it down to usage of mx.controls.Alert. Test
> case is
> > included in this issue [1].
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=evkgF0%2BsdYs2Irz1Jigsgmn6Yq4IS7e4LLvGCJ4EReY%3D&reserved=0
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Thursday, May 7, 2020 10:35 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I think you can verify by debugging in some other browser
> and see
> > if breakpoints get set.
> >
> > A common “bug” in Flex modules was to reference and link the
> > module class into the loading app. I have no idea what will happen
> if you
> > have such a situation in Royale. You can look at the loading app’s
> > link-report to see if the module (Test1) is linked in the app and
> probably
> > see if Test1.js is in the output of the app if you start clean and
> do not
> > compile the module.
> >
> > HTH,
> > -Alex
> >
> > From: Yishay Weiss <yi...@hotmail.com>
> > Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Date: Thursday, May 7, 2020 at 12:26 PM
> > To: "dev@royale.apache.org" <de...@royale.apache.org>
> > Subject: RE: Modules in IE
> >
> > url is
> >
> >
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>>
> >
> > I don’t see errors other than
> >
> > SEC7113: CSS was ignored due to mime type mismatch
> >
> > But I don’t think that’s it.
> >
> > I put a debugger; statement on the first line of the src
> which
> > never kicks.
> >
> >
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58:15 PM
> > To: dev@royale.apache.org <de...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any errors
> > loading and running it? Are the other Royale packages/classes in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something else
> > creates a "window" property at the global window causing our package
> lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > In my example <script> element is there but it’s never
> loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and it
> worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of <script>
> tags in
> > the head. Near the end of the list should be the script for the .js
> file
> > for the module.
> > Do you see any exceptions? ModuleExample works without
> errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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<ma...@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Wednesday, May 6, 2020 7:58 PM
> > Subject: Re: Modules in IE
> >
> > What is the src (url) for that script? Were there any errors
> > loading and running it? Are the other Royale packages/classes in the
> > "window" object?
> >
> > One scenario I thought of is that some bug or something else
> > creates a "window" property at the global window causing our package
> lookup
> > to be off.
> >
> > HTH,
> > -Alex
> >
> > On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
> >
> > In my example <script> element is there but it’s never
> loaded
> > on IE. I can confirm ModuleExamle works.
> >
> > From: Alex Harui<ma...@adobe.com.INVALID>
> > Sent: Sunday, May 3, 2020 9:31 AM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: Modules in IE
> >
> > I just ran examples/royale/ModuleExample in IE and it
> worked.
> > Does it work for you?
> > In the debugger, window.Module and window.MainApp
> resolve to
> > functions. window.org is an object with an apache property.
> > In the DOM Explorer, there should be tons of <script>
> tags in
> > the head. Near the end of the list should be the script for the .js
> file
> > for the module.
> > Do you see any exceptions? ModuleExample works without
> errors.
> >
> > -Alex
> >
> > On 5/2/20, 11:01 AM, "Yishay Weiss" <
> yishayjobs@hotmail.com>
> > wrote:
> >
> > 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<ma...@adobe.com.INVALID>
> > Sent: Thursday, April 30, 2020 6:29 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org>
> > 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" <
> > yishayjobs@hotmail.com> 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:aharui@adobe.com.INVALID
> >
> > Sent: Thursday, April 30, 2020 12:00 AM
> > To: dev@royale.apache.org<mailto:
> dev@royale.apache.org
> > >
> > 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" <
> > yishayjobs@hotmail.com> 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=L0ya5B62P40fyCYZolQxaDCkYF0cbmuDHZhURTCXLPw%3D&reserved=0
>
>
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
RE: Modules in IE
Posted by Yishay Weiss <yi...@hotmail.com>.
> Also, it is possible that inject_html is being overused (…) a static initializer could bring in the code
Do we have an example of static initializers working in Royale? I tried adding some code in curly brackets after the class declaration but I didn’t see it transpiled.
On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
Hi Carlos, thanks. The issue is with inject_html in modules on IE, dialogPolyfill.js just happened to be the target src here. I’ve been searching the net for solutions on IE and I think the trick is to append elements instead of changing the inner html. I see two options of transpiling <inject_html> that would work on IE:
1. Parse the <inject_html> contents in the compiler and create js that would work for IE. Difficult.
2. Replace each line in <inject_html> with dummy elements and change their outerHTML to match each line contents. This one looks easier, but I seem to remember a thread where we were trying to eliminate use of outerHTML.
Any thoughts are welcome.
From: Carlos Rovira<ma...@apache.org>
Sent: Monday, May 11, 2020 6:06 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: Modules in IE
Hi Yishay,
talking without a huge analisys of the problem. I think Jewel Alert works
ok in IE11 so that should mean dialogpolyfil is loading ok. if not the case
something broke recently since I checked that in TDJ and other apps we did.
Anyway, the commit you state is just to give the support we needed. I
didn't tested in IE11, so don't know if we support it. Normally IE11 use to
require
some special way of writing the code for some particular things, so I think
the way to solve this is:
1.- search in SOF or other sources how IE11 expect scripts to be added
dynamically
2.- upgrade the compiler code to use that way with that considerations to
make it IE11 compatible and check if that works for IE11 and rest of
browsers.
sorry to not be able to say much more, but I'm these days with few time
Thanks
El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<yi...@hotmail.com>)
escribió:
> Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in compiler code
> doesn’t work for IE11. Any ideas on how to fix this?
>
> From: Yishay Weiss<ma...@hotmail.com>
> Sent: Monday, May 11, 2020 4:52 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: RE: Modules in IE
>
> These lines in dialogPolyfill.as
>
> * <inject_html>
> * <script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> "></script>
>
> get transpiled to
>
> document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> "></script>'
>
> But that’s making IE11 fail in loading the module. It doesn’t matter what
> the src is, IE will silently fail. For example, I’m getting the same result
> if I replace the above with
>
> document.head.innerHTML += '<script></script>'
>
>
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:35:55 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=UhWgHnDOQVBBCGVW9RI3gwCcxHZcBcYjNu9bfmNEqbI%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=k5fxV4D7kTCIKILQxTYLYkIlTG29sSNaJiJ0gdnXkXM%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:36 PM
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=90IzQjbCvQTqLKnJv4B0q0xP8L7tKRBcGZkeLzsv1hU%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=evkgF0%2BsdYs2Irz1Jigsgmn6Yq4IS7e4LLvGCJ4EReY%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
Carlos Rovira
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=L0ya5B62P40fyCYZolQxaDCkYF0cbmuDHZhURTCXLPw%3D&reserved=0
Re: Modules in IE
Posted by Alex Harui <ah...@adobe.com.INVALID>.
What if we abandon "inject_html" and go with "inject_script" instead? Then when adding to the html output, each script would be wrapped with a <script> tag, but for modules the code could be added to the main module .js file.
Also, it is possible that inject_html is being overused. Any external dependency that isn't required before class initialization probably doesn't need to use inject_html. Depending on the external code, a static initializer could bring in the code, and most of the Application classes have a delayed-start mechanism that could be used as well. I doubt that Alert needs any dependencies before the first call to Alert.show and could even check that it is running on IE before requesting the polyfill get loaded.
My 2 cents,
-Alex
On 5/11/20, 8:36 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
Hi Carlos, thanks. The issue is with inject_html in modules on IE, dialogPolyfill.js just happened to be the target src here. I’ve been searching the net for solutions on IE and I think the trick is to append elements instead of changing the inner html. I see two options of transpiling <inject_html> that would work on IE:
1. Parse the <inject_html> contents in the compiler and create js that would work for IE. Difficult.
2. Replace each line in <inject_html> with dummy elements and change their outerHTML to match each line contents. This one looks easier, but I seem to remember a thread where we were trying to eliminate use of outerHTML.
Any thoughts are welcome.
From: Carlos Rovira<ma...@apache.org>
Sent: Monday, May 11, 2020 6:06 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: Modules in IE
Hi Yishay,
talking without a huge analisys of the problem. I think Jewel Alert works
ok in IE11 so that should mean dialogpolyfil is loading ok. if not the case
something broke recently since I checked that in TDJ and other apps we did.
Anyway, the commit you state is just to give the support we needed. I
didn't tested in IE11, so don't know if we support it. Normally IE11 use to
require
some special way of writing the code for some particular things, so I think
the way to solve this is:
1.- search in SOF or other sources how IE11 expect scripts to be added
dynamically
2.- upgrade the compiler code to use that way with that considerations to
make it IE11 compatible and check if that works for IE11 and rest of
browsers.
sorry to not be able to say much more, but I'm these days with few time
Thanks
El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<yi...@hotmail.com>)
escribió:
> Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in compiler code
> doesn’t work for IE11. Any ideas on how to fix this?
>
> From: Yishay Weiss<ma...@hotmail.com>
> Sent: Monday, May 11, 2020 4:52 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: RE: Modules in IE
>
> These lines in dialogPolyfill.as
>
> * <inject_html>
> * <script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> "></script>
>
> get transpiled to
>
> document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> "></script>'
>
> But that’s making IE11 fail in loading the module. It doesn’t matter what
> the src is, IE will silently fail. For example, I’m getting the same result
> if I replace the above with
>
> document.head.innerHTML += '<script></script>'
>
>
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:35:55 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=UhWgHnDOQVBBCGVW9RI3gwCcxHZcBcYjNu9bfmNEqbI%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=k5fxV4D7kTCIKILQxTYLYkIlTG29sSNaJiJ0gdnXkXM%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:36 PM
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010842741&sdata=tR%2Bwi6nJESMObofdnpDPWv%2BDfqEa0x7MVLjyesc7xZY%3D&reserved=0
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=90IzQjbCvQTqLKnJv4B0q0xP8L7tKRBcGZkeLzsv1hU%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=evkgF0%2BsdYs2Irz1Jigsgmn6Yq4IS7e4LLvGCJ4EReY%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
Carlos Rovira
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C36612d3542e04012022208d7f5c11907%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248082010852737&sdata=L0ya5B62P40fyCYZolQxaDCkYF0cbmuDHZhURTCXLPw%3D&reserved=0
RE: Modules in IE
Posted by Yishay Weiss <yi...@hotmail.com>.
Hi Carlos, thanks. The issue is with inject_html in modules on IE, dialogPolyfill.js just happened to be the target src here. I’ve been searching the net for solutions on IE and I think the trick is to append elements instead of changing the inner html. I see two options of transpiling <inject_html> that would work on IE:
1. Parse the <inject_html> contents in the compiler and create js that would work for IE. Difficult.
2. Replace each line in <inject_html> with dummy elements and change their outerHTML to match each line contents. This one looks easier, but I seem to remember a thread where we were trying to eliminate use of outerHTML.
Any thoughts are welcome.
From: Carlos Rovira<ma...@apache.org>
Sent: Monday, May 11, 2020 6:06 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: Modules in IE
Hi Yishay,
talking without a huge analisys of the problem. I think Jewel Alert works
ok in IE11 so that should mean dialogpolyfil is loading ok. if not the case
something broke recently since I checked that in TDJ and other apps we did.
Anyway, the commit you state is just to give the support we needed. I
didn't tested in IE11, so don't know if we support it. Normally IE11 use to
require
some special way of writing the code for some particular things, so I think
the way to solve this is:
1.- search in SOF or other sources how IE11 expect scripts to be added
dynamically
2.- upgrade the compiler code to use that way with that considerations to
make it IE11 compatible and check if that works for IE11 and rest of
browsers.
sorry to not be able to say much more, but I'm these days with few time
Thanks
El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<yi...@hotmail.com>)
escribió:
> Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in compiler code
> doesn’t work for IE11. Any ideas on how to fix this?
>
> From: Yishay Weiss<ma...@hotmail.com>
> Sent: Monday, May 11, 2020 4:52 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: RE: Modules in IE
>
> These lines in dialogPolyfill.as
>
> * <inject_html>
> * <script src="
> https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js
> "></script>
>
> get transpiled to
>
> document.head.innerHTML += '<script src="
> https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js
> "></script>'
>
> But that’s making IE11 fail in loading the module. It doesn’t matter what
> the src is, IE will silently fail. For example, I’m getting the same result
> if I replace the above with
>
> document.head.innerHTML += '<script></script>'
>
>
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:35:55 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=I%2FM82zvauRqwSBfdRH%2F0Jaim32tLAdFHuwSY6p4JHsg%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=I%2FM82zvauRqwSBfdRH%2F0Jaim32tLAdFHuwSY6p4JHsg%3D&reserved=0%22%3e%3c/script
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=YLSJzDtpgffu0JMpejIWgthMsKkatnxNh29UltYZCw8%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=ApIOBVZfPwSt2mLOqpqOb3QL5O%2BRSeED5fdkEqD741Y%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:36 PM
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=I%2FM82zvauRqwSBfdRH%2F0Jaim32tLAdFHuwSY6p4JHsg%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=I%2FM82zvauRqwSBfdRH%2F0Jaim32tLAdFHuwSY6p4JHsg%3D&reserved=0%22%3e%3c/script
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=YLSJzDtpgffu0JMpejIWgthMsKkatnxNh29UltYZCw8%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=ApIOBVZfPwSt2mLOqpqOb3QL5O%2BRSeED5fdkEqD741Y%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Modules in IE
Posted by Carlos Rovira <ca...@apache.org>.
Hi Yishay,
talking without a huge analisys of the problem. I think Jewel Alert works
ok in IE11 so that should mean dialogpolyfil is loading ok. if not the case
something broke recently since I checked that in TDJ and other apps we did.
Anyway, the commit you state is just to give the support we needed. I
didn't tested in IE11, so don't know if we support it. Normally IE11 use to
require
some special way of writing the code for some particular things, so I think
the way to solve this is:
1.- search in SOF or other sources how IE11 expect scripts to be added
dynamically
2.- upgrade the compiler code to use that way with that considerations to
make it IE11 compatible and check if that works for IE11 and rest of
browsers.
sorry to not be able to say much more, but I'm these days with few time
Thanks
El lun., 11 may. 2020 a las 16:12, Yishay Weiss (<yi...@hotmail.com>)
escribió:
> Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in compiler code
> doesn’t work for IE11. Any ideas on how to fix this?
>
> From: Yishay Weiss<ma...@hotmail.com>
> Sent: Monday, May 11, 2020 4:52 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: RE: Modules in IE
>
> These lines in dialogPolyfill.as
>
> * <inject_html>
> * <script src="
> https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js
> "></script>
>
> get transpiled to
>
> document.head.innerHTML += '<script src="
> https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js
> "></script>'
>
> But that’s making IE11 fail in loading the module. It doesn’t matter what
> the src is, IE will silently fail. For example, I’m getting the same result
> if I replace the above with
>
> document.head.innerHTML += '<script></script>'
>
>
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:35:55 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=I%2FM82zvauRqwSBfdRH%2F0Jaim32tLAdFHuwSY6p4JHsg%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=I%2FM82zvauRqwSBfdRH%2F0Jaim32tLAdFHuwSY6p4JHsg%3D&reserved=0%22%3e%3c/script
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=YLSJzDtpgffu0JMpejIWgthMsKkatnxNh29UltYZCw8%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=ApIOBVZfPwSt2mLOqpqOb3QL5O%2BRSeED5fdkEqD741Y%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 7:36 PM
> Subject: Re: Modules in IE
>
> Does dialog-polyfill load correctly? Does it muck with the window object?
>
> On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> Test1.js isn’t different, but Test1_deps.js is.
>
> diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> index 73eccbe..3e1a8a7 100644
> --- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
> +++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
> @@ -211,4 +211,4 @@
> goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js',
> ['org
> goog.addDependency('../../../XML.js', ['XML'], []);
>
> goog.require('Test1');
> -document.head.innerHTML += '<script src="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=I%2FM82zvauRqwSBfdRH%2F0Jaim32tLAdFHuwSY6p4JHsg%3D&reserved=0
> "></script<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=I%2FM82zvauRqwSBfdRH%2F0Jaim32tLAdFHuwSY6p4JHsg%3D&reserved=0%22%3e%3c/script
> >>';document.head.innerHTM
> L += '<link rel="stylesheet" type="text/css" href="
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=YLSJzDtpgffu0JMpejIWgthMsKkatnxNh29UltYZCw8%3D&reserved=0
> ">';
> +
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 10, 2020 6:39 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> Interesting. Just adding import shouldn't affect the output. What is
> the difference between Test1.js with and without that import statement?
>
> -Alex
>
> On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> I’ve narrowed it down to usage of mx.controls.Alert. Test case is
> included in this issue [1].
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=ApIOBVZfPwSt2mLOqpqOb3QL5O%2BRSeED5fdkEqD741Y%3D&reserved=0
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, May 7, 2020 10:35 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I think you can verify by debugging in some other browser and see
> if breakpoints get set.
>
> A common “bug” in Flex modules was to reference and link the
> module class into the loading app. I have no idea what will happen if you
> have such a situation in Royale. You can look at the loading app’s
> link-report to see if the module (Test1) is linked in the app and probably
> see if Test1.js is in the output of the app if you start clean and do not
> compile the module.
>
> HTH,
> -Alex
>
> From: Yishay Weiss <yi...@hotmail.com>
> Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
> Date: Thursday, May 7, 2020 at 12:26 PM
> To: "dev@royale.apache.org" <de...@royale.apache.org>
> Subject: RE: Modules in IE
>
> url is
>
> file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>
>
> I don’t see errors other than
>
> SEC7113: CSS was ignored due to mime type mismatch
>
> But I don’t think that’s it.
>
> I put a debugger; statement on the first line of the src which
> never kicks.
>
>
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58:15 PM
> To: dev@royale.apache.org <de...@royale.apache.org>
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Wednesday, May 6, 2020 7:58 PM
> Subject: Re: Modules in IE
>
> What is the src (url) for that script? Were there any errors
> loading and running it? Are the other Royale packages/classes in the
> "window" object?
>
> One scenario I thought of is that some bug or something else
> creates a "window" property at the global window causing our package lookup
> to be off.
>
> HTH,
> -Alex
>
> On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>
> In my example <script> element is there but it’s never loaded
> on IE. I can confirm ModuleExamle works.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 9:31 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: Modules in IE
>
> I just ran examples/royale/ModuleExample in IE and it worked.
> Does it work for you?
> In the debugger, window.Module and window.MainApp resolve to
> functions. window.org is an object with an apache property.
> In the DOM Explorer, there should be tons of <script> tags in
> the head. Near the end of the list should be the script for the .js file
> for the module.
> Do you see any exceptions? ModuleExample works without errors.
>
> -Alex
>
> On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com>
> wrote:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 6:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <
> yishayjobs@hotmail.com> wrote:
>
> Yes, it works on Chrome and FF.
> window[this.modulename] is undefined. Didn’t check what happens in other
> browsers.
>
> From: Alex Harui<ma...@adobe.com.INVALID>
> Sent: Thursday, April 30, 2020 12:00 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org
> >
> 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" <
> yishayjobs@hotmail.com> 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.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
Carlos Rovira
http://about.me/carlosrovira
RE: Modules in IE
Posted by Yishay Weiss <yi...@hotmail.com>.
Carols, I think 65c67ee27f8d0d068b3e2163445d48cf200cddc3 in compiler code doesn’t work for IE11. Any ideas on how to fix this?
From: Yishay Weiss<ma...@hotmail.com>
Sent: Monday, May 11, 2020 4:52 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: RE: Modules in IE
These lines in dialogPolyfill.as
* <inject_html>
* <script src="https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js"></script>
get transpiled to
document.head.innerHTML += '<script src="https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js"></script>'
But that’s making IE11 fail in loading the module. It doesn’t matter what the src is, IE will silently fail. For example, I’m getting the same result if I replace the above with
document.head.innerHTML += '<script></script>'
From: Alex Harui <ah...@adobe.com.INVALID>
Sent: Sunday, May 10, 2020 7:35:55 PM
To: dev@royale.apache.org <de...@royale.apache.org>
Subject: Re: Modules in IE
Does dialog-polyfill load correctly? Does it muck with the window object?
On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
Test1.js isn’t different, but Test1_deps.js is.
diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js" "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
index 73eccbe..3e1a8a7 100644
--- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
+++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
@@ -211,4 +211,4 @@ goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js', ['org
goog.addDependency('../../../XML.js', ['XML'], []);
goog.require('Test1');
-document.head.innerHTML += '<script src="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=I%2FM82zvauRqwSBfdRH%2F0Jaim32tLAdFHuwSY6p4JHsg%3D&reserved=0"></script<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=I%2FM82zvauRqwSBfdRH%2F0Jaim32tLAdFHuwSY6p4JHsg%3D&reserved=0%22%3e%3c/script>>';document.head.innerHTM
L += '<link rel="stylesheet" type="text/css" href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=YLSJzDtpgffu0JMpejIWgthMsKkatnxNh29UltYZCw8%3D&reserved=0">';
+
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 10, 2020 6:39 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
Interesting. Just adding import shouldn't affect the output. What is the difference between Test1.js with and without that import statement?
-Alex
On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
I’ve narrowed it down to usage of mx.controls.Alert. Test case is included in this issue [1].
[1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=ApIOBVZfPwSt2mLOqpqOb3QL5O%2BRSeED5fdkEqD741Y%3D&reserved=0
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, May 7, 2020 10:35 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I think you can verify by debugging in some other browser and see if breakpoints get set.
A common “bug” in Flex modules was to reference and link the module class into the loading app. I have no idea what will happen if you have such a situation in Royale. You can look at the loading app’s link-report to see if the module (Test1) is linked in the app and probably see if Test1.js is in the output of the app if you start clean and do not compile the module.
HTH,
-Alex
From: Yishay Weiss <yi...@hotmail.com>
Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
Date: Thursday, May 7, 2020 at 12:26 PM
To: "dev@royale.apache.org" <de...@royale.apache.org>
Subject: RE: Modules in IE
url is
file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>
I don’t see errors other than
SEC7113: CSS was ignored due to mime type mismatch
But I don’t think that’s it.
I put a debugger; statement on the first line of the src which never kicks.
From: Alex Harui <ah...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58:15 PM
To: dev@royale.apache.org <de...@royale.apache.org>
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58 PM
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 10, 2020 7:36 PM
Subject: Re: Modules in IE
Does dialog-polyfill load correctly? Does it muck with the window object?
On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
Test1.js isn’t different, but Test1_deps.js is.
diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js" "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
index 73eccbe..3e1a8a7 100644
--- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
+++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
@@ -211,4 +211,4 @@ goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js', ['org
goog.addDependency('../../../XML.js', ['XML'], []);
goog.require('Test1');
-document.head.innerHTML += '<script src="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=I%2FM82zvauRqwSBfdRH%2F0Jaim32tLAdFHuwSY6p4JHsg%3D&reserved=0"></script<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=I%2FM82zvauRqwSBfdRH%2F0Jaim32tLAdFHuwSY6p4JHsg%3D&reserved=0%22%3e%3c/script>>';document.head.innerHTM
L += '<link rel="stylesheet" type="text/css" href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=YLSJzDtpgffu0JMpejIWgthMsKkatnxNh29UltYZCw8%3D&reserved=0">';
+
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 10, 2020 6:39 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
Interesting. Just adding import shouldn't affect the output. What is the difference between Test1.js with and without that import statement?
-Alex
On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
I’ve narrowed it down to usage of mx.controls.Alert. Test case is included in this issue [1].
[1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=ApIOBVZfPwSt2mLOqpqOb3QL5O%2BRSeED5fdkEqD741Y%3D&reserved=0
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, May 7, 2020 10:35 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I think you can verify by debugging in some other browser and see if breakpoints get set.
A common “bug” in Flex modules was to reference and link the module class into the loading app. I have no idea what will happen if you have such a situation in Royale. You can look at the loading app’s link-report to see if the module (Test1) is linked in the app and probably see if Test1.js is in the output of the app if you start clean and do not compile the module.
HTH,
-Alex
From: Yishay Weiss <yi...@hotmail.com>
Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
Date: Thursday, May 7, 2020 at 12:26 PM
To: "dev@royale.apache.org" <de...@royale.apache.org>
Subject: RE: Modules in IE
url is
file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>
I don’t see errors other than
SEC7113: CSS was ignored due to mime type mismatch
But I don’t think that’s it.
I put a debugger; statement on the first line of the src which never kicks.
From: Alex Harui <ah...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58:15 PM
To: dev@royale.apache.org <de...@royale.apache.org>
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58 PM
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
RE: Modules in IE
Posted by Yishay Weiss <yi...@hotmail.com>.
These lines in dialogPolyfill.as
* <inject_html>
* <script src="https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js"></script>
get transpiled to
document.head.innerHTML += '<script src="https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js"></script>'
But that’s making IE11 fail in loading the module. It doesn’t matter what the src is, IE will silently fail. For example, I’m getting the same result if I replace the above with
document.head.innerHTML += '<script></script>'
From: Alex Harui <ah...@adobe.com.INVALID>
Sent: Sunday, May 10, 2020 7:35:55 PM
To: dev@royale.apache.org <de...@royale.apache.org>
Subject: Re: Modules in IE
Does dialog-polyfill load correctly? Does it muck with the window object?
On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
Test1.js isn’t different, but Test1_deps.js is.
diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js" "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
index 73eccbe..3e1a8a7 100644
--- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
+++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
@@ -211,4 +211,4 @@ goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js', ['org
goog.addDependency('../../../XML.js', ['XML'], []);
goog.require('Test1');
-document.head.innerHTML += '<script src="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=I%2FM82zvauRqwSBfdRH%2F0Jaim32tLAdFHuwSY6p4JHsg%3D&reserved=0"></script<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=I%2FM82zvauRqwSBfdRH%2F0Jaim32tLAdFHuwSY6p4JHsg%3D&reserved=0%22%3e%3c/script>>';document.head.innerHTM
L += '<link rel="stylesheet" type="text/css" href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=YLSJzDtpgffu0JMpejIWgthMsKkatnxNh29UltYZCw8%3D&reserved=0">';
+
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 10, 2020 6:39 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
Interesting. Just adding import shouldn't affect the output. What is the difference between Test1.js with and without that import statement?
-Alex
On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
I’ve narrowed it down to usage of mx.controls.Alert. Test case is included in this issue [1].
[1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=ApIOBVZfPwSt2mLOqpqOb3QL5O%2BRSeED5fdkEqD741Y%3D&reserved=0
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, May 7, 2020 10:35 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I think you can verify by debugging in some other browser and see if breakpoints get set.
A common “bug” in Flex modules was to reference and link the module class into the loading app. I have no idea what will happen if you have such a situation in Royale. You can look at the loading app’s link-report to see if the module (Test1) is linked in the app and probably see if Test1.js is in the output of the app if you start clean and do not compile the module.
HTH,
-Alex
From: Yishay Weiss <yi...@hotmail.com>
Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
Date: Thursday, May 7, 2020 at 12:26 PM
To: "dev@royale.apache.org" <de...@royale.apache.org>
Subject: RE: Modules in IE
url is
file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>
I don’t see errors other than
SEC7113: CSS was ignored due to mime type mismatch
But I don’t think that’s it.
I put a debugger; statement on the first line of the src which never kicks.
From: Alex Harui <ah...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58:15 PM
To: dev@royale.apache.org <de...@royale.apache.org>
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58 PM
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 10, 2020 7:36 PM
Subject: Re: Modules in IE
Does dialog-polyfill load correctly? Does it muck with the window object?
On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
Test1.js isn’t different, but Test1_deps.js is.
diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js" "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
index 73eccbe..3e1a8a7 100644
--- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
+++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
@@ -211,4 +211,4 @@ goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js', ['org
goog.addDependency('../../../XML.js', ['XML'], []);
goog.require('Test1');
-document.head.innerHTML += '<script src="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=I%2FM82zvauRqwSBfdRH%2F0Jaim32tLAdFHuwSY6p4JHsg%3D&reserved=0"></script<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=I%2FM82zvauRqwSBfdRH%2F0Jaim32tLAdFHuwSY6p4JHsg%3D&reserved=0%22%3e%3c/script>>';document.head.innerHTM
L += '<link rel="stylesheet" type="text/css" href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=YLSJzDtpgffu0JMpejIWgthMsKkatnxNh29UltYZCw8%3D&reserved=0">';
+
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 10, 2020 6:39 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
Interesting. Just adding import shouldn't affect the output. What is the difference between Test1.js with and without that import statement?
-Alex
On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
I’ve narrowed it down to usage of mx.controls.Alert. Test case is included in this issue [1].
[1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=ApIOBVZfPwSt2mLOqpqOb3QL5O%2BRSeED5fdkEqD741Y%3D&reserved=0
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, May 7, 2020 10:35 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I think you can verify by debugging in some other browser and see if breakpoints get set.
A common “bug” in Flex modules was to reference and link the module class into the loading app. I have no idea what will happen if you have such a situation in Royale. You can look at the loading app’s link-report to see if the module (Test1) is linked in the app and probably see if Test1.js is in the output of the app if you start clean and do not compile the module.
HTH,
-Alex
From: Yishay Weiss <yi...@hotmail.com>
Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
Date: Thursday, May 7, 2020 at 12:26 PM
To: "dev@royale.apache.org" <de...@royale.apache.org>
Subject: RE: Modules in IE
url is
file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>>
I don’t see errors other than
SEC7113: CSS was ignored due to mime type mismatch
But I don’t think that’s it.
I put a debugger; statement on the first line of the src which never kicks.
From: Alex Harui <ah...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58:15 PM
To: dev@royale.apache.org <de...@royale.apache.org>
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58 PM
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
Re: Modules in IE
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Does dialog-polyfill load correctly? Does it muck with the window object?
On 5/10/20, 9:13 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
Test1.js isn’t different, but Test1_deps.js is.
diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js" "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
index 73eccbe..3e1a8a7 100644
--- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
+++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
@@ -211,4 +211,4 @@ goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js', ['org
goog.addDependency('../../../XML.js', ['XML'], []);
goog.require('Test1');
-document.head.innerHTML += '<script src="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.js&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=I%2FM82zvauRqwSBfdRH%2F0Jaim32tLAdFHuwSY6p4JHsg%3D&reserved=0"></script>';document.head.innerHTM
L += '<link rel="stylesheet" type="text/css" href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fdialog-polyfill%2F0.4.9%2Fdialog-polyfill.min.css&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=YLSJzDtpgffu0JMpejIWgthMsKkatnxNh29UltYZCw8%3D&reserved=0">';
+
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 10, 2020 6:39 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
Interesting. Just adding import shouldn't affect the output. What is the difference between Test1.js with and without that import statement?
-Alex
On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
I’ve narrowed it down to usage of mx.controls.Alert. Test case is included in this issue [1].
[1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C573afcb12b92475b779408d7f4fd196a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247240200485983&sdata=ApIOBVZfPwSt2mLOqpqOb3QL5O%2BRSeED5fdkEqD741Y%3D&reserved=0
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, May 7, 2020 10:35 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I think you can verify by debugging in some other browser and see if breakpoints get set.
A common “bug” in Flex modules was to reference and link the module class into the loading app. I have no idea what will happen if you have such a situation in Royale. You can look at the loading app’s link-report to see if the module (Test1) is linked in the app and probably see if Test1.js is in the output of the app if you start clean and do not compile the module.
HTH,
-Alex
From: Yishay Weiss <yi...@hotmail.com>
Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
Date: Thursday, May 7, 2020 at 12:26 PM
To: "dev@royale.apache.org" <de...@royale.apache.org>
Subject: RE: Modules in IE
url is
file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>
I don’t see errors other than
SEC7113: CSS was ignored due to mime type mismatch
But I don’t think that’s it.
I put a debugger; statement on the first line of the src which never kicks.
From: Alex Harui <ah...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58:15 PM
To: dev@royale.apache.org <de...@royale.apache.org>
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58 PM
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
RE: Modules in IE
Posted by Yishay Weiss <yi...@hotmail.com>.
Test1.js isn’t different, but Test1_deps.js is.
diff --git "a/.\\dir_with_import\\/js-debug/Test1__deps.js" "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
index 73eccbe..3e1a8a7 100644
--- "a/.\\dir_with_import\\/js-debug/Test1__deps.js"
+++ "b/.\\dir_without_import\\/js-debug/Test1__deps.js"
@@ -211,4 +211,4 @@ goog.addDependency('../../../org/apache/royale/graphics/GradientEntry.js', ['org
goog.addDependency('../../../XML.js', ['XML'], []);
goog.require('Test1');
-document.head.innerHTML += '<script src="https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.js"></script>';document.head.innerHTM
L += '<link rel="stylesheet" type="text/css" href="https://cdnjs.cloudflare.com/ajax/libs/dialog-polyfill/0.4.9/dialog-polyfill.min.css">';
+
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 10, 2020 6:39 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
Interesting. Just adding import shouldn't affect the output. What is the difference between Test1.js with and without that import statement?
-Alex
On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
I’ve narrowed it down to usage of mx.controls.Alert. Test case is included in this issue [1].
[1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C8556ec4e409c4cdedf4908d7f4f7450d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247215164707057&sdata=9dKdWRWEc8k%2BPiJKHyXLaEvliVHF8o6GK6s5iLonkvo%3D&reserved=0
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, May 7, 2020 10:35 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I think you can verify by debugging in some other browser and see if breakpoints get set.
A common “bug” in Flex modules was to reference and link the module class into the loading app. I have no idea what will happen if you have such a situation in Royale. You can look at the loading app’s link-report to see if the module (Test1) is linked in the app and probably see if Test1.js is in the output of the app if you start clean and do not compile the module.
HTH,
-Alex
From: Yishay Weiss <yi...@hotmail.com>
Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
Date: Thursday, May 7, 2020 at 12:26 PM
To: "dev@royale.apache.org" <de...@royale.apache.org>
Subject: RE: Modules in IE
url is
file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js%3cfile:/C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>>
I don’t see errors other than
SEC7113: CSS was ignored due to mime type mismatch
But I don’t think that’s it.
I put a debugger; statement on the first line of the src which never kicks.
From: Alex Harui <ah...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58:15 PM
To: dev@royale.apache.org <de...@royale.apache.org>
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58 PM
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
Re: Modules in IE
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Interesting. Just adding import shouldn't affect the output. What is the difference between Test1.js with and without that import statement?
-Alex
On 5/10/20, 8:31 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
I’ve narrowed it down to usage of mx.controls.Alert. Test case is included in this issue [1].
[1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F826&data=02%7C01%7Caharui%40adobe.com%7C8556ec4e409c4cdedf4908d7f4f7450d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637247215164707057&sdata=9dKdWRWEc8k%2BPiJKHyXLaEvliVHF8o6GK6s5iLonkvo%3D&reserved=0
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, May 7, 2020 10:35 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I think you can verify by debugging in some other browser and see if breakpoints get set.
A common “bug” in Flex modules was to reference and link the module class into the loading app. I have no idea what will happen if you have such a situation in Royale. You can look at the loading app’s link-report to see if the module (Test1) is linked in the app and probably see if Test1.js is in the output of the app if you start clean and do not compile the module.
HTH,
-Alex
From: Yishay Weiss <yi...@hotmail.com>
Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
Date: Thursday, May 7, 2020 at 12:26 PM
To: "dev@royale.apache.org" <de...@royale.apache.org>
Subject: RE: Modules in IE
url is
file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>
I don’t see errors other than
SEC7113: CSS was ignored due to mime type mismatch
But I don’t think that’s it.
I put a debugger; statement on the first line of the src which never kicks.
From: Alex Harui <ah...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58:15 PM
To: dev@royale.apache.org <de...@royale.apache.org>
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58 PM
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
RE: Modules in IE
Posted by Yishay Weiss <yi...@hotmail.com>.
I’ve narrowed it down to usage of mx.controls.Alert. Test case is included in this issue [1].
[1] https://github.com/apache/royale-asjs/issues/826
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, May 7, 2020 10:35 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I think you can verify by debugging in some other browser and see if breakpoints get set.
A common “bug” in Flex modules was to reference and link the module class into the loading app. I have no idea what will happen if you have such a situation in Royale. You can look at the loading app’s link-report to see if the module (Test1) is linked in the app and probably see if Test1.js is in the output of the app if you start clean and do not compile the module.
HTH,
-Alex
From: Yishay Weiss <yi...@hotmail.com>
Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
Date: Thursday, May 7, 2020 at 12:26 PM
To: "dev@royale.apache.org" <de...@royale.apache.org>
Subject: RE: Modules in IE
url is
file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js<file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/Test1.js>
I don’t see errors other than
SEC7113: CSS was ignored due to mime type mismatch
But I don’t think that’s it.
I put a debugger; statement on the first line of the src which never kicks.
From: Alex Harui <ah...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58:15 PM
To: dev@royale.apache.org <de...@royale.apache.org>
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58 PM
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
Re: Modules in IE
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I think you can verify by debugging in some other browser and see if breakpoints get set.
A common “bug” in Flex modules was to reference and link the module class into the loading app. I have no idea what will happen if you have such a situation in Royale. You can look at the loading app’s link-report to see if the module (Test1) is linked in the app and probably see if Test1.js is in the output of the app if you start clean and do not compile the module.
HTH,
-Alex
From: Yishay Weiss <yi...@hotmail.com>
Reply-To: "dev@royale.apache.org" <de...@royale.apache.org>
Date: Thursday, May 7, 2020 at 12:26 PM
To: "dev@royale.apache.org" <de...@royale.apache.org>
Subject: RE: Modules in IE
url is
file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js
I don’t see errors other than
SEC7113: CSS was ignored due to mime type mismatch
But I don’t think that’s it.
I put a debugger; statement on the first line of the src which never kicks.
From: Alex Harui <ah...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58:15 PM
To: dev@royale.apache.org <de...@royale.apache.org>
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58 PM
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
RE: Modules in IE
Posted by Yishay Weiss <yi...@hotmail.com>.
url is
file:///C:/dev/RoyaleComponentTest/NewComponentTest/bin/js-debug/library/closure/goog/../../../Test1.js
I don’t see errors other than
SEC7113: CSS was ignored due to mime type mismatch
But I don’t think that’s it.
I put a debugger; statement on the first line of the src which never kicks.
From: Alex Harui <ah...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58:15 PM
To: dev@royale.apache.org <de...@royale.apache.org>
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Wednesday, May 6, 2020 7:58 PM
Subject: Re: Modules in IE
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
Re: Modules in IE
Posted by Alex Harui <ah...@adobe.com.INVALID>.
What is the src (url) for that script? Were there any errors loading and running it? Are the other Royale packages/classes in the "window" object?
One scenario I thought of is that some bug or something else creates a "window" property at the global window causing our package lookup to be off.
HTH,
-Alex
On 5/6/20, 8:47 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
RE: Modules in IE
Posted by Yishay Weiss <yi...@hotmail.com>.
In my example <script> element is there but it’s never loaded on IE. I can confirm ModuleExamle works.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 9:31 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Modules in IE
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.
Re: Modules in IE
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I just ran examples/royale/ModuleExample in IE and it worked. Does it work for you?
In the debugger, window.Module and window.MainApp resolve to functions. window.org is an object with an apache property.
In the DOM Explorer, there should be tons of <script> tags in the head. Near the end of the list should be the script for the .js file for the module.
Do you see any exceptions? ModuleExample works without errors.
-Alex
On 5/2/20, 11:01 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
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<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 6:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> wrote:
Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Thursday, April 30, 2020 12:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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.