Found in GWT Release: All to date (I'm using 1.5.2 though)

Detailed description: See http://www.quirksmode.org/presentations/tae08/StateOfTheBrowsers.pdf PPK gives use some advice on how to effectively do browser detection in JavaScript. Given the need to detect "rendering engines" rather than "browsers" (WebKit, whether it is Safari, Chrome or Adobe AIR), maybe only one such change is needed: namely, use window.opera to detect Opera (with which you can "mask as IE" and the userAgent won't contain Opera at all).

Workaround if you have one: A property-providers can still be overriden in your own module...

For the record, Opera people recommend using window.opera too: http://developer.yahoo.com/yui/theater/video.php?v=bovens-opera

Closing as a result of issue triage. More information can be found here:

http://groups.google.com/group/google-web-toolkit/browse_thread/thread/3a7bf1c6a3d35431

Thanks

This is still true as of GWT 2.0, and people are running into issues because of this (see issue 4206)

Opera is moving to Chromium (see also issue 8005). They already published a beta for Windows and OSX and it's likely to be released before the next GWT release.