There is new feature in the

mrksem454 — Tue, 13 Apr 2010 05:42:13 +0000

There is new feature in the CSS 3 Specification in the form of -moz-max-content, -moz-min-content, -moz-fit-content, and -moz-available values to width, min-width, and max-width. And also Wrapped whitespace (white-space: pre-wrap), This allows you to have a < pre/> whose contents are wrapped nicely, while still maintaining its rigid structure.

Thanx webwiz, that seems to

Jack Michaelson — Fri, 04 Dec 2009 08:43:06 +0000

Thanx webwiz, that seems to be the trick. Tested in IE7+, Opera, Safari, FF2, FF3.5 and Chrome. This is all Win, but I will test it on OSX tonight.

Yeah I know about the doctype, but thanx anyway These buttons are extracted from a bigger project and I just made a quick example to post here at TWF. I used an old editor that automaticly generates this incomplete doctype. Should have replaced it though...

thanks again
Jack

P.S. You are using an

webwiz — Fri, 04 Dec 2009 06:21:38 +0000

P.S. You are using an incomplete DOCTYPE, which puts browsers in "quirks mode." This explanation of quirks mode gives the gory details. In brief, while the only consequential effect of quirks on real browsers is to make box sizes include borders and padding, compared to the standard of content only, all versions of the problem child work like the totally bizarre Internet Explorer 5.5. This includes IE 8.

Oh - and as if Microsoft had not given us enough problems, you'll need to know about IE8 "compatibility view" and add the new META tag. But get your DOCTYPE right first...

Hmm. That's an odd one! It

webwiz — Thu, 03 Dec 2009 22:05:59 +0000

Hmm. That's an odd one! It seems that the 11px margin-left on the span pushes the text to the right, but not the containing box. (?) I tried adding margin-right: -11px; to the rule for a.button span {} which seemed to fix FF 2 without disturbing my other browsers. I have not checked on a Windows box, though-- don't know what the problem child will make of it.