GWT doesn't promise to make your application look the same on all browsers. It does try its very best to make sure that the JS it produces functions the same across browsers, and doesn't leave any nasty side effects, leak memory, or anything like that.
There may be some cases where GWT will leverage CSS "tricks" on each browser to achieve a result (although I can't think of any such cases off the top of my head), but that doesn't mean that GWT will take steps to ensure that all of your CSS is magically transformed into something that works on any browser. For one thing, that's out of scope, and for another it isn't possible. Some things in CSS just aren't supported, especially in older browsers. On Thu, Jul 22, 2010 at 1:35 PM, Magnus <alpineblas...@googlemail.com>wrote: > Hi, > > sorry for repeating: > > I thought that the promise of GWT was that one never ever has to deal > with such problems anymore? > > Why are we discussing about wether to spent time in supporting IE6 > while the GWT compiler should do this? > > Magnus > > -- > 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<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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.
