Hi Thomas, Do you happen to have any link with the rationale for this?
I can understand that having elemental2.dom.Document and com.google.gwt.dom.client.Document in the same java file may be somewhat confusing. However I believe to be able to map directly js code to java without the need to put (mentally) everywhere Js is a good thing. On Tue, Feb 6, 2018 at 12:31 AM, Thomas Broyer <[email protected]> wrote: > Native types have been renamed with a Js prefix: > https://static.javadoc.io/com.google.elemental2/elemental2- > core/1.0.0-RC1/elemental2/core/JsRegExp.html > > -- > 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. > -- Vassilis Virvilis -- 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.
