Tuesday, June 25, 2013

Re: Anchor does not work in IE - very strange problem!

but why was this exception not reported as others client-side exceptions are?

In IE + DevMode you would have seen a NullPointerException on the console. If you use Chrome/Firefox + DevMode you never see the problem because both browser support the Audio element and thus its never null.

In DevMode, GWT automatically registers a DefaultUncaughtExceptionHandler that logs uncaught exceptions to the console. This only happens in DevMode and not if you have compiled your app. Thus if you dont have set your own UncaughtExceptionHandler in your app's onModuleLoad() you will never see uncaught exceptions once your app is compiled.

So always set an UncaughtExceptionHandler on your own and do what you want to do with that exception. For example I display an information message that something unexpected has happened and then send the exception to the server where it gets logged and a new issue is automatically created in an issue tracker.

-- J.

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment