Not all bugs are IE’s, and Chimera’s CSS implementation isn’t always perfect. Every CSS spec I read says:
An element’s padding is the amount of space between the border and the content of the element.
So setting padding:10px; should not cause the border of a box to move – it should cause the contained content to be pushed in, as with the padding attribute for table cells. But no… Chimera pushes the DIV boundary out instead, forking up the design. This is solvable by creating a new containing class and applying the padding on that. Not elegant, but seems to work in all CSS browsers.
Update: As far as I can tell, this is the official bug report on the issue. Scanning through the comments is an object lesson in just how difficult it can be for browser makers to interpret the W3C’s recommendations. The Mozilla team really cares, but even with the requisite will-power, some ambiguities are difficult to resolve. Kind of like Biblical or Constitutional interpretation — except that in this case the framers are still alive ;)
5 Replies to “padding:10px;”
You should search bugzilla and file a bug if necessary….
Chimera uses Mozilla 1.0, so it is possible that this bug has already been fixed in the two releases of gecko (1.1 and 1.2) since the release of 1.0.
Hmm, this probably isn’t related, because Chimera should support the CSS Box Model — but it may be worth a look:
Unfortunately padding can be a hit or miss deal.
Thanks for pointing that out. No, not fixed, but acknowledged. Unfortunately it’s a P3 bug. Bummer. At least there are viable workarounds.
Dan, that’s an excellent tip, thanks. Although in that case, it’s IE that gets it wrong, Mozilla gets it right. So I don’t think it’s *quite* the same bug. Grrr..
Ah, you’re right… wondered if a particular version of mozilla had the same issues. Guess not. Very annoying.