On 30 mar, 23:44, Jason Essington <[email protected]> wrote:
> Well, all versions up to the current GWT 1.5x all work with IE6, so,
> as long as you are developing for a legacy browser, I see nothing
> wrong with using an old version of your toolkit if it comes to that.
How about the upcoming 1.6?
My understanding is that it doesn't break IE6 (X-UA-Compatible: IE=7
isn't totaly supported yet, so GWT is only "fully" compatible with X-
UA-Compatible: IE=5 AFAICT, which means it "supports IE6") but can we
count on it for the final release?
I'm in the very same situation as Remy/Starman (well, I don't the
"why" but IE6 is our customer's "standard browser") and I'd like to
migrate to 1.6 to use the new event handlers to "connect" my
"modules" (using "logical" events) as part of a big refactoring.
> But in reality, deferred binding allows you to continue having a
> separate javascript payload for IE6, so I see no reason why it
> wouldn't be possible to support IE6 indefinitely. Though at some point
> it might be up to you to continue that support.
...and the real question is: now that IE8 is "final", (when) will GWT
support X-UA-Compatible: IE=8? (notably, there's a *big* issue with
ImageBundle --and other ClippedImage-- rendering)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
