That's a valid point I had not considered. I had some reservations about using the HTML 5 tag because I had read that IE 6 had no idea what to do with new doctypes. I did a little further reading, it turns out that the HTML 5 doctype should kick it into strict mode, which is something of an approximation of standards mode. It's at least not as ghastly a perversion of CSS and the DOM as their version of quirks mode.
>From what I can tell, the Relative->Absolute positioning pattern Google likes to use for its standards mode panels has limited success in IE 6. Perhaps they do have some work around, but from I've seen of the classes they've been pretty stubborn with it. I haven't gotten to the stage with my latest application (first in GWT since 2.0) where I've considered testing and writing custom IE 6 cases. I am expecting fun times ahead. Hope that helps! On Jun 10, 10:46 pm, Chris Lercher <[email protected]> wrote: > Daniel, IE 6 does have something "like" a standards mode - it's not > really standards compliant, but it does behave differently, when > putting it into that mode. That's because, when it's in quirks mode, > then it behaves like IE 5.5. Seehttp://www.quirksmode.org/css/quirksmode.html > for more details. > > As far as I can tell, the new layout panels of GWT 2.x are designed to > also work on IE6 in its "standards" mode - sometimes by emulating CSS > properties with javascript. > > @Ata: Try to use <!DOCTYPE html> (note the uppercase DOCTYPE). Make > sure, that it's the very first thing in the document (no comments or > anything in front of it!) > > On Jun 10, 2:28 pm, Daniel Le Clere <[email protected]> wrote: > > > > > Ummm... IE 6 doesn't have a standards mode... Adding that doctype is > > probably just causing more issues. The HTML 5 doctype is useful for > > forcing IE 7 and 8 into standards mode. If you want to get your > > program rolling for IE 6 you're going to have to write some specific > > views under the MVC or accept greater restrictions in your overall > > design. GWT is not magic, it cannot force IE 6 to do something that > > was not accounted for in its design. If you want that kind of magic > > try Google Frame :) > > > On Jun 10, 12:37 pm, Ata <[email protected]> wrote: > > > > > In GWT some widgets only work properly in quirks or standard mode, not > > > > both. As far as I could tell I should be running the app in standard > > > > mode because I have <!doctype html> as the first line of the root HTML > > > > page, however widgets like TabLayoutPanel that are supposed to work in > > > > standard mode don't work, and the quirks mode ones do. I'm using IE6 > > > > (I can also try with chrome and IE8 later, but it should work with any > > > > browser). Does anyone know why this quirks/standard mode is not > > > > working as advertised? Could it be a browser thing, or am I really NOT > > > > in standard mode even though I think I am, or is the GWT documentation > > > > just lying to me? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
