Re: Tapestry 5.6.1 and IE11

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

Re: Tapestry 5.6.1 and IE11

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 --

Re: Tapestry 5.6.1 and IE11

Hi, minification can always be a problem, we ran into issues in other frameworks / languages, too... Instead of disabling Minification for all files, or for a single browser, you could also just replace the Google Closure compiler with a more selective one: https://gist.github.com/benweidig/db9

Re: Tapestry 5.6.1 and IE11

Hi Volker, I do not want to disable minifaction at all. Maybe some other pieces of code can be effected. I like the idea from Ben as well and tried to integrate it within /contributeRequestHandler(OrderedConfiguration config, final RequestGlobals requestGlobals)/, with no success. Thank you both

Re: Tapestry 5.6.1 and IE11

Hello Ben + Hakan Not sure if this is off topic, but I experienced a minification-related problem also - across various browser types, not only IE 11. Page loading mask ("spinning wheel") never disappears. Problem also is in core.js as I understand the JS debugger. See my comments in TAP5-2605

Re: Tapestry 5.6.1 and IE11

I played with this a bit. In the AppModule it is also possible using /contributeRequestHandler/-method(see below)   public static void contributeRequestHandler(OrderedConfiguration config,                     final RequestGlobals requestGlobals){         RequestFilter filter = new RequestFilter()

Re: Tapestry 5.6.1 and IE11

Okey thank you very much. I do not like the idea to disable minimizer itself. Maybe Tapestry uses a lot of JS and CSS as minimizer. This can have a big effect, during the runtime and the web app lost his functions. If their is an other opportunity, that will be great. But currently it seems this i

Re: Tapestry 5.6.1 and IE11

Yes, that's the closure compiler: https://github.com/google/closure-compiler/issues/3280 The effect of the symbol is that no minimizer won't be run, so no CSS and JS minification. We added a request filter to restrict disabling minification to IE11: @Contribute(RequestHandler.class) public

Re: Tapestry 5.6.1 and IE11

Thank you for your response. The error message occurs on core.js(121,20). I put the screenshot and the cursor shows the position 20 below. Disabling MINIFICATION_ENABLED worked. I can not see the error on the console any more. But did that has an effect for the web app in production mode? I am u

Re: Tapestry 5.6.1 and IE11

Hi, does the problem occur in production only, or also in dev? We had some issues with Google Closure Compiler and IE11 in the past, optimizing "too much". You could try to disable minification to narrow the problem down: org.apache.tapestry5.SymbolConstants.MINIFICATION_ENABLED Or you can chec

Tapestry 5.6.1 and IE11

Hi there, I have a issue, when I am starting my web app (Tapestry 5.6.1) with IE 11. I receive the following error message in every page load. The effect is, that jQuery is not loading correctly and I can not use jQuery in my web app. Do you have an idea, how I can solve this? Is their any work ar

Tapestry 5.6.1 and IE11

Hi there, I have a issue, when I am starting my web app (Tapestry 5.6.1) with IE 11. I receive the following error message in every page load. The effect is, that jQuery is not loading correctly and I can not use jQuery in my web app. Do you have an idea, how I can solve this? Is their any work ar