Ok, I can undertand what you said. But, in your Shoucase example the differences are acceptable. In my case the direfferences makes my application unusable in FF. I thought this could be justa a div display block instead of inline, or something like that. But... my mistake... Thanks a lot
On Sat, Nov 15, 2008 at 4:15 PM, gregor <[EMAIL PROTECTED]>wrote: > > Hi jsantaelena, > > Even one pixel will the do the damage if you have two widgets right up > against each other. if you run Showcase from here: > > http://gwt.google.com/samples/Showcase/Showcase.html#CwCheckBox > > and open it full screen in both IE & FF, you will see (by switching > their window tabs, this makes it obvious) that it is actually slightly > different in each browser, the extent of the difference depending on > which example you select (at least it is in my IE & FF setups, but > that's the point isn't it). > > Now if you look through the Showcase code to see why a particular > example of interest is different between IE & FF you find it probably > has to do with the "box model" issue. I haven't done this with > Showcase, but I did it with its previous GWT 1.4.x incarnation > KitchenSink when I faced exactly your problem last year. So > unfortunately I can't point you to the exact code/CSS that > demonstrates it in Showcase. In 1.4.x KitchenSink you can see it > clearly in the HorizontalSplitPanel demo. > > Google don't seem to care that it looks slightly different (pixel for > pixel) in IE & FF because as an application it works perfectly well in > both browsers. The way they design UI's makes the difference > irrelevant. Notice the spacings between the widgets. But if you design > a layout that puts widgets right up against each other, a more windows/ > desktop style UI design so to speak, you suddenly run into trouble > with this "box model" problem (whereas Google seem to walk around it > by designing the problem out). > > Some might say that the Google GWT team, faced with competition from > Ext-JS (and their "extended family" of GWT-Ext wrappers) are being > reluctantly dragged, kicking and screaming, into a more "windows > friendly" approach. Others might argue that in reality it is Google > who are dragging us die hard desktop/business application programmers, > similarly kicking and screaming, into a 21st century where the likes > of GWT and Gears are swiftly making the Windows desktop paradigm old > hat - Web 3.0 perhaps. FWIW I started 2007 in the former camp, I am > now in the latter. > > Anyway enough musing. It is possible to make a cross-browser Windows > style UI with GWT but you have to do some extra work depending on > exactly what you want to do. > > regards > gregor > > On Nov 15, 2:06 pm, jsantaelena <[EMAIL PROTECTED]> wrote: > > I'm not setting large border (1px or 2px) and i'm not using margins or > > padding. > > > > Why not happens with GWT Showcase? > > > > Another intersting thing is, after each refresh, FF renders my > > applicatios more massed. > > > > I'm using this DOCTYPE: > > > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" " > http://www.w3.org/TR/html4/loose.dtd";> > > > > And my CSS just sets fonts, colors, backgrounds... > > > > On 15 nov, 08:43, gregor <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > Are you using any borders/margins/padding with your panels? If you are > > > this is might be the cause of your problem > > > > > Google "IE broken box model". You will find info about the difference > > > between how IE and FF (and other browsers) handle borders etc . > > > Basically the issue is this: say you have a panel that is set to 100px > > > X 100px, and you add a 5px border to it. IE renders this 100 x 100 > > > total (so the actual box is now 90 x 90), whereas FF renders it as 110 > > > x 110 total (so the actual box remains 100 x 100). Another way of > > > looking at it is that FF works "from inside out" whereas IE works > > > "from outside in". Actually the FF approach follows W3C standards > > > whereas IE does not (hence "IE broken box model"). > > > > > In some situations GWT deals with this automatically for you, in > > > others it doesn't. You will find a lot of different approaches to > > > dealing with this on the net using javascript/CSS techniques because > > > this problem has been around a long time. With GWT there are a range > > > of more Java oriented techniques available revolving around how you go > > > about nesting and separating primary display containers and their > > > contents. > > > > > If you create a short EntryPoint test class that demonstrates your > > > particular issue and post it here I'm sure you will get a range of > > > solution options suggested. > > > > > regards > > > gregor > > > > > On Nov 15, 2:32 am, reechard <[EMAIL PROTECTED]> wrote: > > > > > > yes -- I am experiencing this. Wondering if I need to use some kind > of > > > > browser-specific CSS style to fix it... > > > > > > On Nov 14, 5:29 pm, jsantaelena <[EMAIL PROTECTED]> wrote: > > > > > > > Hi all, > > > > > > > My GWT application render very well in IE, but in FF the panels > > > > > (VerticalPanes, HorizontalPanels and FlexTables) overlaps, all of > > > > > them. > > > > > > > Have somebody expereinced this? > > > > > > > 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 -~----------~----~----~----~------~----~------~--~---
