<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Float vs. Inline-Block</title>
	<atom:link href="http://www.ternstyle.us/blog/float-vs-inline-block/feed" rel="self" type="application/rss+xml" />
	<link>http://www.ternstyle.us/blog/float-vs-inline-block</link>
	<description>web solutions for the happy developer and the disgruntled site owner</description>
	<lastBuildDate>Fri, 03 Feb 2012 14:34:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.ternstyle.us/blog/float-vs-inline-block/comment-page-1#comment-1494</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 03 Feb 2012 14:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ternstyle.us/?p=1757#comment-1494</guid>
		<description>Once IE 6 and 7 become obsolete inline-blocks should become more prevalent than floats.</description>
		<content:encoded><![CDATA[<p>Once IE 6 and 7 become obsolete inline-blocks should become more prevalent than floats.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Kettner</title>
		<link>http://www.ternstyle.us/blog/float-vs-inline-block/comment-page-1#comment-1493</link>
		<dc:creator>Thomas Kettner</dc:creator>
		<pubDate>Tue, 24 Jan 2012 09:27:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ternstyle.us/?p=1757#comment-1493</guid>
		<description>Great Article! Not only from a technical perspective but also easy to read and perfectly stressed.
Thanks for that.</description>
		<content:encoded><![CDATA[<p>Great Article! Not only from a technical perspective but also easy to read and perfectly stressed.<br />
Thanks for that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Myke</title>
		<link>http://www.ternstyle.us/blog/float-vs-inline-block/comment-page-1#comment-1492</link>
		<dc:creator>Myke</dc:creator>
		<pubDate>Thu, 29 Dec 2011 21:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ternstyle.us/?p=1757#comment-1492</guid>
		<description>probably one of the most informative posts i&#039;ve ever read about floats and display-inline. Thank you SOOOO much for this article.</description>
		<content:encoded><![CDATA[<p>probably one of the most informative posts i&#8217;ve ever read about floats and display-inline. Thank you SOOOO much for this article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Walton</title>
		<link>http://www.ternstyle.us/blog/float-vs-inline-block/comment-page-1#comment-1491</link>
		<dc:creator>Richard Walton</dc:creator>
		<pubDate>Thu, 24 Nov 2011 19:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ternstyle.us/?p=1757#comment-1491</guid>
		<description>Great article. Answered all of my questions.
I think I&#039;ll be sticking with floats, for the most part.</description>
		<content:encoded><![CDATA[<p>Great article. Answered all of my questions.<br />
I think I&#8217;ll be sticking with floats, for the most part.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dinesh Ramakrishnan</title>
		<link>http://www.ternstyle.us/blog/float-vs-inline-block/comment-page-1#comment-1490</link>
		<dc:creator>Dinesh Ramakrishnan</dc:creator>
		<pubDate>Wed, 12 Oct 2011 12:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ternstyle.us/?p=1757#comment-1490</guid>
		<description>Great article... this addresses many confusions between float and in-line block usages.</description>
		<content:encoded><![CDATA[<p>Great article&#8230; this addresses many confusions between float and in-line block usages.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larseirik</title>
		<link>http://www.ternstyle.us/blog/float-vs-inline-block/comment-page-1#comment-1483</link>
		<dc:creator>Larseirik</dc:creator>
		<pubDate>Wed, 06 Jul 2011 09:24:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ternstyle.us/?p=1757#comment-1483</guid>
		<description>Great article. Makes it easier for me as a developer to understand the whoe css layout issues.</description>
		<content:encoded><![CDATA[<p>Great article. Makes it easier for me as a developer to understand the whoe css layout issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Cambridge</title>
		<link>http://www.ternstyle.us/blog/float-vs-inline-block/comment-page-1#comment-1473</link>
		<dc:creator>Robert Cambridge</dc:creator>
		<pubDate>Thu, 21 Apr 2011 09:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ternstyle.us/?p=1757#comment-1473</guid>
		<description>overflow:hidden has it&#039;s consequences (any non-floated child elements outside of the parent&#039;s visible area will not expand the box).

The default is overflow: visible.

Use overflow: auto :)</description>
		<content:encoded><![CDATA[<p>overflow:hidden has it&#8217;s consequences (any non-floated child elements outside of the parent&#8217;s visible area will not expand the box).</p>
<p>The default is overflow: visible.</p>
<p>Use overflow: auto <img src='http://www.ternstyle.us/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.ternstyle.us/blog/float-vs-inline-block/comment-page-1#comment-1323</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 20 Oct 2010 00:42:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.ternstyle.us/?p=1757#comment-1323</guid>
		<description>Jacob,

Wow. Great work. Thanks for this post and for doing the research.

I like the zoom technique and the IE 6 hack saves an HTTP request by eliminating the conditional stylesheet as long as it isn&#039;t needed otherwise. (I use the conditional stylesheets as a matter of preference. I try to only use CSS hacks at this point in my back-end design where functionality matters more than aesthetics and compliance.)

I have to say, I&#039;m not a huge fan of the negative word-space and letter-spacing. Granted, it&#039;s a similar amount of CSS commands but what if a browser&#039;s default letter and word spacing differs from the one you choose to offset. Setting the font-size to zero, I think is fool proof and cross-browser compatible.</description>
		<content:encoded><![CDATA[<p>Jacob,</p>
<p>Wow. Great work. Thanks for this post and for doing the research.</p>
<p>I like the zoom technique and the IE 6 hack saves an HTTP request by eliminating the conditional stylesheet as long as it isn&#8217;t needed otherwise. (I use the conditional stylesheets as a matter of preference. I try to only use CSS hacks at this point in my back-end design where functionality matters more than aesthetics and compliance.)</p>
<p>I have to say, I&#8217;m not a huge fan of the negative word-space and letter-spacing. Granted, it&#8217;s a similar amount of CSS commands but what if a browser&#8217;s default letter and word spacing differs from the one you choose to offset. Setting the font-size to zero, I think is fool proof and cross-browser compatible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Wright</title>
		<link>http://www.ternstyle.us/blog/float-vs-inline-block/comment-page-1#comment-1322</link>
		<dc:creator>Dave Wright</dc:creator>
		<pubDate>Tue, 19 Oct 2010 08:51:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.ternstyle.us/?p=1757#comment-1322</guid>
		<description>I have always used a clear fix div class, I wasn&#039;t aware of the overflow:hidden technique however, this seems much cleaner, you&#039;ve converted me!</description>
		<content:encoded><![CDATA[<p>I have always used a clear fix div class, I wasn&#8217;t aware of the overflow:hidden technique however, this seems much cleaner, you&#8217;ve converted me!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob</title>
		<link>http://www.ternstyle.us/blog/float-vs-inline-block/comment-page-1#comment-1320</link>
		<dc:creator>Jacob</dc:creator>
		<pubDate>Thu, 14 Oct 2010 14:13:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.ternstyle.us/?p=1757#comment-1320</guid>
		<description>Thank you very much for this post. I think all in all (like most layout techniques) they both shine in their own regard and for their own specific situations (as you pointed out).

But, that being said I think that the inline-block method should be at least written about more. Perhaps I have just been thick but I don&#039;t think I&#039;ve seen it used much at all, and maybe it&#039;s because of the white-space issue, but I also think its infrequency is also due to obscurity. 

All that aside though - I wanted to point out how yahoo seems to be handling the whitespace issue (this is the method they are using for their grid v3).

for the elements that are being rendered inline-block they have set the following properties:

        display:inline-block;
	zoom:1;
*display:inline;
	letter-spacing:normal;
	word-spacing:normal;
	vertical-align:top;

things to note in this:
  1. the *hack is being used to slice out the ie rendering like you did in the conditional stylesheet. (either or, do what you like)
  2. zoom:1 fixes some display issue I think with the way ie7 handles the display:inline (regardless, the display:inline + zoom:1 make this thing work in ie7)
  3. the word-spacing and letter-spacing are to reverse the next thing they are doing which directly addresses your white-space concern.

The following styles are applied to the parent of the inline elements in question (in your example, the ul):

        letter-spacing:-0.31em;
	*letter-spacing:normal;
	word-spacing:-0.43em;

I haven&#039;t fully fleshed out this whole thing but it seems to handle the white-space issue you described.  Anyway, I think at the least it&#039;s worth further investigation.  Thanks again for the post.</description>
		<content:encoded><![CDATA[<p>Thank you very much for this post. I think all in all (like most layout techniques) they both shine in their own regard and for their own specific situations (as you pointed out).</p>
<p>But, that being said I think that the inline-block method should be at least written about more. Perhaps I have just been thick but I don&#8217;t think I&#8217;ve seen it used much at all, and maybe it&#8217;s because of the white-space issue, but I also think its infrequency is also due to obscurity. </p>
<p>All that aside though &#8211; I wanted to point out how yahoo seems to be handling the whitespace issue (this is the method they are using for their grid v3).</p>
<p>for the elements that are being rendered inline-block they have set the following properties:</p>
<p>        display:inline-block;<br />
	zoom:1;<br />
*display:inline;<br />
	letter-spacing:normal;<br />
	word-spacing:normal;<br />
	vertical-align:top;</p>
<p>things to note in this:<br />
  1. the *hack is being used to slice out the ie rendering like you did in the conditional stylesheet. (either or, do what you like)<br />
  2. zoom:1 fixes some display issue I think with the way ie7 handles the display:inline (regardless, the display:inline + zoom:1 make this thing work in ie7)<br />
  3. the word-spacing and letter-spacing are to reverse the next thing they are doing which directly addresses your white-space concern.</p>
<p>The following styles are applied to the parent of the inline elements in question (in your example, the ul):</p>
<p>        letter-spacing:-0.31em;<br />
	*letter-spacing:normal;<br />
	word-spacing:-0.43em;</p>
<p>I haven&#8217;t fully fleshed out this whole thing but it seems to handle the white-space issue you described.  Anyway, I think at the least it&#8217;s worth further investigation.  Thanks again for the post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

