Thanks, we'll add that to our blacklist. Do we also need to define the blacklist with, e.g., <define-configuration-property name="js.identifier.blacklist" is-multi- valued="true" /> or is it already defined elsewhere by GWT?
Thanks, Dan On Fri, Nov 29, 2019 at 6:34 PM 'Axel' via GWT Users < [email protected]> wrote: > The obfuscator does not have "u2f" as a blacklisted identifier. In > conjunction with a Firefox that now (>=67) has U2F enabled by default (see > about:config, security.webauth.u2f) the identifier "window.u2f" is made > available. When the obfuscator uses u2f as an output symbol, weird things > can happen, such as properties that are expected to be found on the object > bound to the obfuscated "u2f" identifier not being found because u2f points > to the U2F object and not the application object. > > In our project we work around this by adding > > <extend-configuration-property name="js.identifier.blacklist" > value="u2f"/> > > to a base module that all our modules inherit. I think this should become > part of the standard as it is error prone and incredibly time-consuming to > figure out the root cause of the errors that can result. > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/google-web-toolkit/470b1dd1-4133-464c-b523-7feab71f87ba%40googlegroups.com > <https://groups.google.com/d/msgid/google-web-toolkit/470b1dd1-4133-464c-b523-7feab71f87ba%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CABTxsEMUm4Sumbs7GH2PXAMStU44%2B8WvLEXtESwL3QDrUfxXGA%40mail.gmail.com.
