Re: Do browser permutations matter with JsInterop?

2020-09-25 Thread anb...@gmail.com
That's what I was trying to ask: Does Core use permutations, but I didn't know how to phrase it correctly. If it's just used for stack traces then I'm going to collapse all. Thank you!! This will save me a lot of compiling time. On Friday, September 25, 2020 at 2:14:11 AM UTC-10

Re: Do browser permutations matter with JsInterop?

2020-09-25 Thread Thomas Broyer
Actually, even Core uses permutations, for exception stacktraces collection: https://github.com/gwtproject/gwt/blob/master/user/src/com/google/gwt/core/CoreWithUserAgent.gwt.xml Fwiw, if everything compiled down to the same code, there'd be a single *.cache.js output, so it wouldn't matter

Re: Do browser permutations matter with JsInterop?

2020-09-25 Thread Jens
JsInterop is just a convention, so permutations don't make sense here. Elemental2 is generated from a specification, so it does not use permutations. If you use Elemental2 you are responsible to apply polyfills in browsers that do not support the JS features you are using via elemental2.

Do browser permutations matter with JsInterop?

2020-09-24 Thread anb...@gmail.com
If I am using JsInterop and Elemental2 rather than the legacy GWT classes for DOM manipulations, event registration, etc. do I still need to compile permutations for various browsers? Or will different browser permutations essentially compile to the same thing? -- You received this message