Safari is supported AFAIK. Chrome would be too since it is Webkit like Safari, although I don't know how much QA effort goes towards it - probably minimal for three reasons: 1) it uses the same engine as Safari 2) it has minimal browser share 3) it's Google's browser that they want as standards compliant as possible, meaning few/no browser-specific workarounds are necessary (& since there's only 1 version with a 2nd on the way, it's not much of an issue).
The combination of 1 & 2 make spending time on heavy QA of Chrome explicitly (outside of maybe some unofficial smoke tests) probably unlikely. However, I have no idea what the process is internally, so my guess could be way off. On Tue, May 12, 2009 at 4:52 PM, Salvador Diaz <[email protected]>wrote: > > > http://code.google.com/webtoolkit/doc/1.6/FAQ_GettingStarted.html#Browsers_and_Servers > > It should be noted however that this doesn't mean that "GWT is not > preferred to be deployed on Chrome or Safari" just that there will > probably be some layout differences. > > There are almost always workarounds for layout differences, it's just > a matter of making choices and compromises. > > Cheers, > > Salvador > > On May 12, 9:39 pm, Blessed Geek <[email protected]> wrote: > > Rather, it is more accurate to say that I set the absolute distance of > > the panels 90px from the top of the root panel - to make room for page > > logo and header text. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
