GWT does not promise that all renderings look the same, but instead gives you the tools to do so efficiently. For example, IE does not render borders around empty cells in a table, but FF and webkit do. It is up to you to set the CSS to tell IE to also render them. The IE widgets do promise to do what they can to make them behave consistently across browsers and provide the most efficient implementation, but the only thing that promises consistent rendering is the new layout panels. It is up to you to write the CSS for all the browser quirks. The way that IE calculates table layout is significantly different than the other browsers in some cases and I think that with fairly minimal tweaking you will be able to fix these issues. Make sure you specifically set cellpadding and cellspacing to 0 (IE assumes non-zero for one of these, don't remember which).
On Jul 22, 12:03 pm, Brett Thomas <brettptho...@gmail.com> wrote: > I think it looks classy to display a note for IE6 users that says something > along the lines of "unfortunately our website no longer supports IE6, click > here to learn how to upgrade" > > I think plenty of people have no idea what browser version they are using. > They may know the difference between IE and Firefox, but not what version > number it is. If a site doesn't work, they'll just say "must be because my > computer is old" and forget about it. So, tell them what they can do to fix > it... > > On Thu, Jul 22, 2010 at 2:00 PM, charlie <charlie.f...@gmail.com> wrote: > > Agreed. It's been the bane of web developers existence for far too long. > > > On Thu, Jul 22, 2010 at 12:44 PM, Christian Goudreau < > > goudreau.christ...@gmail.com> wrote: > > >> Let's drop IE6 and IE7 support, I think it's time anyway for that. > > >> On Thu, Jul 22, 2010 at 1:42 PM, Isaac Truett <itru...@gmail.com> wrote: > > >>> 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-toolkit@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. > > >> -- > >> Christian Goudreau > > >> -- > >> 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. > > > -- > > <charlie/> > > > -- > > 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.
