I didn't know about the "callback error function".

How/where can I register such a callback?


On 27 Jan., 12:34, Thomas Broyer <t.bro...@gmail.com> wrote:
> On Jan 27, 2:22 am, dmen <dmenou...@gmail.com> wrote:
>
> > How future proof are GWT compilations? For example, if I compile my
> > app today with 2.0:
>
> > 1. How it will react in a couple of years to lets say IE 9, Firefox 4,
> > etc.?
>
> > 2. How it will react to a yet unknown, however standards compatible,
> > browser?
>
> It all depend how these browsers get detected by the GWT bootstrap
> code (*.nocache.js; particularly the <property-provider
> name="user.agent"> code).
> New versions should be detected as the highest version supported by
> GWT (IE9 detected as user.agent=ie8 –well, depending on the X-UA-
> Compatible of course–, and Firefox 4 as user.agent=gecko1_8), so
> unless there are breaking changes in their JS API and/or they "break
> workarounds", your app should run OK.
> As for new browsers, same as above, it depends how they are detected.
> If they're detected as an already supported browser *and* they are
> compatible with it, then all is OK (this wass the case for Chrome,
> which is detected as user.agent=safari; sure it uses the same WebKit
> rendering engine, but a different JS engine, which could have
> introduced incompatibilities, but that's not the case AFAICT),
> otherwise the app won't load at all (you can define a "callback error
> function" though to have some JavaScript run in this eventuality)

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to