Sounds like a bug - you should file a bug (under the issues tab of the googlecode page). GWT's goal is that you shouldn't care about the browser *unless you're doing some JSNI stuff).
If you figure out a workaround in code, you can hide it behind a deferred interface & the GWT compiler will take care of everything for you. Also, I would recommend testing against Opera and/or Safari to provide a little more perspective when you file the bug. On Tue, Mar 10, 2009 at 3:17 PM, DavidPShaw <wowkr...@gmail.com> wrote: > > We have a gwt widget that works great in FF, but in IE the Dialog box > has serious clipping problems. The problem is demonstrated here: > > We've traced the problem to the fact that the page holding the root > div and the folder containing the GWT output are different. > > The source of the page contains the gwt reference as a virtual url to > a subfolder deeper in the site. > > If the content of the gwt.PreferredISPUI is copied into the same > folder as the jsp (and the path is changed to reflect that the > nocache.js is in the same folder), it works fine. > > Is there something we need to do to make the dialog render properly in > IE without putting all the files in the folder with the jsp? > > > > --~--~---------~--~----~------------~-------~--~----~ 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-Toolkit@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 -~----------~----~----~----~------~----~------~--~---