No. I would recommend running in hosted mode on windows, although it's highly unlikely that'll solve anything (since any GWT code you write runs in the JVM anyways & thus has no browser-dependant code outside of the GWT framework). Without knowing more about what the app is doing, it's hard to say - that code snippet should work.
Can you supply the code for the entry point? On Mon, Apr 27, 2009 at 5:24 PM, Ben <[email protected]> wrote: > > Are you suggesting me to develop on Windows? > > My development environment is Mac OS X, but I do not think that is the > reason why my app is not working on both IE 6 and IE 7 (I know GWT > does not support IE 8 well for now). So for me, the hosted mode is > Safari, but I have tested out on Safari on Mac, Firefox on Mac Firefox > on Windows, all work. But it does not work at all on both IE 6 and IE > 7. And as I said, my app is pure GWT, no JSNI and other stuff. Do you > have any idea why it does not work on IE? > > Thanks, > Ben > > On Apr 27, 1:20 pm, Vitali Lovich <[email protected]> wrote: > > Have you run in hosted mode? On Windows it's a flavour of IE5 or IE6 > > (probably 6). IE8 support was added recently to trunk, so official > support > > won't come out until the next version of GWT (unless they do a point > release > > with support, although that seems unlikely). IE8 isn't even out yet. > > > > On Mon, Apr 27, 2009 at 12:15 PM, Ben <[email protected]> wrote: > > > > > I am building an application with newest release of GWT on Mac OS. The > > > whole app is in GWT, no JSNI and the structure of the application is > > > sorta complicated. I have couple Composite widgets and some Composite > > > widgets have references of other Composite Widgets. For example: > > > > > A extends Composite { > > > } > > > > > B extends Composite { > > > A a = new A(); > > > > > public B (A instance_a) { > > > this.a = instance_a > > > } > > > } > > > > > And after compile and deployment, my application works fine in Firefox > > > and Safari, but it has JS error on all IE 6, 7 and 8. And I did some > > > debug by putting Window.alert(msg) in the end of Entry Point and I > > > found out one of my composite widget causes the problem. Once I > > > exclude it from Entry Point. The Window.alert is able to execute in IE > > > 6,7 and 8. According to the documentation, GWT should have pretty good > > > support for both IE 6 and 7. Does anyone have any idea what could be > > > the possible reason for this kind of incompatibility? > > > > > Thanks > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
