CSS is silly

[Deja Q]

One piece of code to position the main menu...

Konqueror displays the menu a tad too high...
Firefox displays it rather a bit too low...
IE displays it correctly; but I've removed all other formatting and making it CSS-centric
Opera displays it correctly!!! (so IE bashing isn't allowed this time... :( )

:crazy: :crazy: :crazy: :crazy: :crazy: :crazy: :crazy: :crazy: :crazy: :crazy: :crazy: :crazy:

[RoyGBiv]

1. Do you have words?

As in, does the menu have text characters? If so, it could be a font issue with FF and Konqueror, the latter because of font issues with Linux itself (and also FF if you're running it under Linux). I had the same problem with a menu bar, and it turned out to be a font issue.

[mainegreen]

2. I like CSS, 'cept for the box model.

The box model is silly and doesn't work right.

Silly box model.

[charlie]

3. No kidding

The "wrong" model is the intuitive, practical one. And all the padded, bordered blocks shoved into sized divs I've seen around the web tells me we're far from alone. The W3C oughta take note of the crapload of nonsemantic markup spawned by their unwieldy style dictum.

Be glad their original clipping foolishness never got traction. It worked like this: the default values for an unclipped region were 0,0,0,0. Clipping outward was done with negative values, inward positive. So, if you had a box that needed widening on the right and left, it looked like this -- clip:rect(0,-5px,0,-5px). This was actually implemented in early Netscape/Mozilla builds and caused a floodstorm of WHAT THE FUCK ARE YOU GUYS UP TO mail. The recommendation was changed in the next revision.

http://www.w3.org/TR/REC-CSS2/visufx.html#clipping
http://www.w3.org/TR/CSS21/visufx.html#clipping