Hi Bruno, you are correct on pretty much all points, here is my thinking:
> Mixture of display: table / table-cell / inline-block may work for such
> cases in most browsers, but the mixture that you have got now is a bit
> strange... You have:
>
> .featureItem2 {
> display: table-cell;
> }
> /*\*/
> html .featureItem2 {
> display: inline-block;
> }
> /**/
>
> The second rule overrides the first, so all browsers that support
> inline-block use that one. I guess your intention was to feed the second
> rule to IE only.
Yes, this was my intention. My (incorrect) assumption was that inline-block
would be ignored by all but IE. Instead of the * hack I counted on the
specificity weight rules: html .featureItem2 is more specific than
.featureItem2 so it will take precedent in browsers that support it. In a
"duh" moment I realized that I had this backwards and have since made the IE
rules less specific and I think the problem may be solved (at least until
IE8 comes out). Browser tests would be greatly appreciated.
http://www.basalweb.com/test/dltest3.html
> - table-cell and inline-blocks have different behaviors. If in your case
> you
> may have so many (or so big) blocks that they do not fit in a 'line' the
> results will differ (do you want them to wrap or to overflow?) You should
> also check the case of blocks not all having the same height (unless you
> set
> a fixed height for them.)
I added more content to one of the "cells" on the test page. The result was
fine in all except IE which required vertical-align:top to pull the shorter
contents of adjacent spans to the top. I think, hopefully, that the only
issue left unresolved is that of equal block height in IE...
Thanks,
Michael
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
