> I am testing on Windows 10, Chrome, JDK 1.8.0_111. I also reproduced the > issue in Firefox, edge and IE11. >
Compile your app for production but use -style PRETTY so you can better search in the final JS output. Then search the method name containing your failing code and compare the generated JS. If it works in SuperDevMode but fails at production then it might be an optimization bug in GWT. But that is something you can only figure out when looking at the generated JS code. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
