While reskinning this site, I’ve found some weird CSS irregularities
- KHTML-based browsers position absolute elements wrong; they’re offset from the border edge, instead of the padding edge. This was a clarification added in CSS 2.1. Mozilla already follows the newer spec, which can lead to difficulties if you want to support both browsers. You’ll have to remove the padding from your containing block, and add it back on the child elements, except for the absolutely-positioned one.
- You can no longer use negative coordinates for absolutely positioning elements in Mozilla. I have no idea when this changed, and it doesn’t make much sense to me. But in order to, for example, get the -1px offset needed to have a corner image overlap it’s containing block’s border (like the cut corner on the navigation on this site), you must set your top/left/bottom/right to 0, and use a negative margin. Tested on Firefox 1.0.3.
- You can use
url() in a content property to display an image. Slick!
⚛