All your numbers are ending up even so I can’t think it’s the odd-number bug.ītw you keep mentioning height tags… I’m thinking you mean the height declarations in your CSS? But you do still have those on the James McM siteĪlso, do you have access to another type of computer (PC or linux)? So far, my FF on Linux and on Windows are doing ok at default font sizes (which does possibly suggest something with FF/Mac). So can you get them to line up at all in your Firefox by, for example, removing the padding or the border of a single image? (as a test). So, they should not only fit, but fit with room. The total allotted inner space is 940px (the 960 inner room of bgbodytext minus the padding of the wrapping p) and the total width of three images is bringing me to 932px (but I suck at math so don’t quote me on that). Ok thanks for the link on that one… I had tried your earlier one by trying to merge the two bad links but it didn’t work…Īnyway, in Firefox on Linux the images are making nice rows. Vertical-align: bottom / making images blocks or block-context (like floats) also removes the space, but sometimes you don’t want them acting like blocks/īorder: 0 / since usually I don’t want borders/ So in my little part of my CSS sheet where I have “resets”, I usually have something like this: In case you haven’t run across it, there also this thing with images, which sometimes only appears in Firefox (but really ought to show in everyone): inline images will be treated like text (because they are inline) and have a bit of space underneath them (to make room for the dangly parts of letters, known as descenders) which sometimes may hit you when you’re not expecting it. Opera on the other hand seems more independent of windowing system. My FF is sensitive to the fact that my Desktop runs on Gnome, making fonts a bit bigger and making things wrap on Linux when they don’t wrap on Windows.
#Firefox for mac troubleshooting code
Plus I’m still thinking differences between FF on OSes is influenced mostly by the windowing system, so code could not differentiate anyway. It’s generally cleaner than hacking and frankly, nobody knows if you have 20px of padding vs 18px of padding, with the exception of when you are lining an element up with an image or the edge of a container who’s edges are visible.
However I come across similar situations now and then and when I have as much empty space around things as you have, I instead change paddings or whatever until all browsers comply.
0 kommentar(er)
