See
https://stackoverflow.com/questions/28727070/gwt-2-7-warn-users-they-are-using-an-unsupported-browser
(beware that those properties use eval() so are possibly unsafe and/or
won't work under a strict CSP; you could customize the
CrossSiteIframeLinker with a different processMetas.js that doesn't use
eval())
Alternatively, use <set-property-fallback> to avoid the error, then use
UserAgent in your entry point to check the browser and bail out.
On Monday, March 11, 2019 at 1:58:55 AM UTC+1, Craig Mitchell wrote:
>
> As it was an uncaught exception, I was able to catch it in a global
> handler. Not a great solution, but it works.
>
> <script type="text/javascript">
> window.onerror = function myErrorHandler(errorMsg, url, lineNumber) {
> if (navigator.appVersion.indexOf("MSIE 7.") != -1) {
> alert("Sorry, IE7 is not supported.");
> } else {
> alert("An unexpected error occurred: " + errorMsg);
> }
> return false;
> }
> </script>
>
>
> Any better ideas will be much appreciated. :-)
>
--
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.
