You shouldn't have to compile the source code differently depending on the browser. Depending on what browser is loading the main javascript (which GWT gets compiled into), a special .js is loaded for that browser.
That being said, some times I've personally noticed things like formatting have been off on one then the other. Spacing, IMAGES especially, slight colors, things like that. What is different about FF and IE in your case? Is it the lack of CSS in FF? I would use Firebug to examine your CSS, make sure everything is there. I've had small bugs in my css, like too many brackets or something like that. IE will ignore it and parse the rest of the CSS fine, FF will ignore everything below the bug making the page look off. I've started putting new CSS in the beginning of my page so it's pretty obvious when FF finds a bug and ignores the rest of the CSS. On Jul 27, 1:01 am, harkon <victor.sauerm...@googlemail.com> wrote: > Hi! > > During development of a complete GWT client server application in > hosted mode, I hosted the app in an apache tomcat web container. > When I start the application in the Microsoft Internet Explorer the > screen shows exactly the same design as shown in hosted mode. But > viewed in Firefox does not. > Whats wrong here? > Do I have to compile the client sources differently? > If yes, what do I have to do in order to reach the correct client > source from used browser? > > Cheers > harkon --~--~---------~--~----~------------~-------~--~----~ 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 For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
