Re: Do browser permutations matter with JsInterop?

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 much whether you compile for various browsers or not (besides compilation time). Seeing more than one *.cache.js means there are differences, and if those differences are minimal you may want to <collapse-all-properties /> or at a minimum <collapse-property name="user.agent" values="*" />

On Friday, September 25, 2020 at 9:55:43 AM UTC+2, Jens wrote:

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. However there might be usages of permutations in other GWT code you might using, things like GWT-RPC, RequestFactory, .....

-- J.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/5a50afbf-39d3-46d8-ab2d-36907e401da1o%40googlegroups.com.