Figured something along those lines. Thanks Joel. sfm
On Tue, Dec 8, 2009 at 4:22 PM, Joel Webber <[email protected]> wrote: > That should be fixed in the final release. Turns out I had made the mistake > of writing style.setProperty("float", "left"), rather than > style.setProperty("cssFloat", "left"). The latter is "correct", but WebKit > accepts either. > > (Yes, there should be a style.setFloat() method, but that will have to come > later, once I have time to write a script to generate the bazillion CSS > property setters!) > > On Tue, Dec 8, 2009 at 4:17 PM, Stuart Moffatt <[email protected]>wrote: > >> @jgw, >> >> Morten makes a good observation (which I wasn't worrying about for now as >> I just chalked it up to pre-release fuzzies). >> >> Any ideas why the rendering in FF is so poor? It seems we might be heading >> back to the land where web developers need a PhD in browser quirks (albeit >> CSS instead of JS) >> >> sfm >> >> On Tue, Dec 8, 2009 at 4:10 PM, Morten Holm <[email protected]> wrote: >> >>> On 3 Dec., 21:53, Stuart Moffatt <[email protected]> wrote: >>> > And here is what it should look like: >>> > >>> > http://tablayoutpanel.latest.emcode-dev.appspot.com >>> > >>> >>> This looks great in Safari, but not so good in FireFox. Any idea why? >>> >>> Morten >> >> >> -- >> http://groups.google.com/group/Google-Web-Toolkit-Contributors >> > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
