Hi, the console log you've posted is an error due to Google Closure Compiler replacing unicode that it deems safe with the actual unicode characters. Some unicode whitespace is supposed to be "safe", but IE11 doesn't think so and your error occurs.
There's no option in Google Closure Compiler to disable this replacement, as far as I know. That's why replacing the minimizer with a custom version and deactivating minification for some files is a workaround. The core.js file is actually JavaScript stack, which is a combination of many different JS files: https://github.com/apache/tapestry-5/blob/4fcd88f92c7e6e2ab21551d2c7248871e8d8938b/tapestry-core/src/main/java/org/apache/tapestry5/modules/JavaScriptModule.java#L143-L212 One if this files is "underscore". Check out the actual source code of underscore and compare it with your console log to see it's the origin of the IE problem: https://github.com/apache/tapestry-5/blob/73e327b4f8/tapestry-core/src/main/resources/META-INF/assets/tapestry5/underscore-1.8.3.js#L1401 Ben On Thu, Oct 29, 2020 at 10:03 AM Hakan Sahin <sa...@avetana.de> wrote: > Hi Ben, > > thank you for your solution. > > I have troubles with core.js (121,20) on IE. The error has an effect to > not loading JSON-functions in background. I do not know, is it depended > with GCM or not? > > Thank you and take care. Best regards > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > >
