<?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: Eliminating whitespace after display:inline-block elements</title>
	<atom:link href="http://nerd.vasilis.nl/remove-whitespace-inline-block/feed/" rel="self" type="application/rss+xml" />
	<link>http://nerd.vasilis.nl/remove-whitespace-inline-block/</link>
	<description>Vasilis van Gemert</description>
	<lastBuildDate>Thu, 11 Aug 2011 03:54:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Vasilis</title>
		<link>http://nerd.vasilis.nl/remove-whitespace-inline-block/#comment-211</link>
		<dc:creator>Vasilis</dc:creator>
		<pubDate>Thu, 20 May 2010 20:53:27 +0000</pubDate>
		<guid isPermaLink="false">http://nerd.vasilis.nl/?p=126#comment-211</guid>
		<description>I came to the conclusion that you shouldn&#039;t use display:inline-block if you wnat a pixel perfect layout. Since I really can&#039;t be bothered by single pixel differences I&#039;m not even thinking of trying to find a solution for this webkit/gecko thing. 
But it&#039;s certainly a good thing that people should be warned about the possible shortcomings of this technique, so thanks a lot for your feedback, Jason!</description>
		<content:encoded><![CDATA[<p>I came to the conclusion that you shouldn&#8217;t use display:inline-block if you wnat a pixel perfect layout. Since I really can&#8217;t be bothered by single pixel differences I&#8217;m not even thinking of trying to find a solution for this webkit/gecko thing.<br />
But it&#8217;s certainly a good thing that people should be warned about the possible shortcomings of this technique, so thanks a lot for your feedback, Jason!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jason Kuhrt</title>
		<link>http://nerd.vasilis.nl/remove-whitespace-inline-block/#comment-210</link>
		<dc:creator>jason Kuhrt</dc:creator>
		<pubDate>Thu, 20 May 2010 20:45:20 +0000</pubDate>
		<guid isPermaLink="false">http://nerd.vasilis.nl/?p=126#comment-210</guid>
		<description>I seem to have found an issue where in Webkit there is a 1px gap but in FF (Gecko) there is no gap. Fixing the 1px gap in Webkit means losing 1px in FF.

Anyone else having this issue?</description>
		<content:encoded><![CDATA[<p>I seem to have found an issue where in Webkit there is a 1px gap but in FF (Gecko) there is no gap. Fixing the 1px gap in Webkit means losing 1px in FF.</p>
<p>Anyone else having this issue?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jason Kuhrt</title>
		<link>http://nerd.vasilis.nl/remove-whitespace-inline-block/#comment-209</link>
		<dc:creator>jason Kuhrt</dc:creator>
		<pubDate>Thu, 20 May 2010 20:22:09 +0000</pubDate>
		<guid isPermaLink="false">http://nerd.vasilis.nl/?p=126#comment-209</guid>
		<description>It seems like this solution doesn&#039;t have too many implications for future overhead / typography complications. The only other solution I&#039;ve seen as elegant is a javascript solution. See it here: http://mrclay.org/tests/inline-block-whitespace.html

I&#039;m thinking that maybe the JS version should be used and have this CSS method called upon as a backup if JS is turned off.

But if this proves robust enough then maybe that&#039;s not needed.

Cheers</description>
		<content:encoded><![CDATA[<p>It seems like this solution doesn&#8217;t have too many implications for future overhead / typography complications. The only other solution I&#8217;ve seen as elegant is a javascript solution. See it here: <a href="http://mrclay.org/tests/inline-block-whitespace.html" rel="nofollow">Klik!</a></p>
<p>I&#8217;m thinking that maybe the JS version should be used and have this CSS method called upon as a backup if JS is turned off.</p>
<p>But if this proves robust enough then maybe that&#8217;s not needed.</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mathias Bynens</title>
		<link>http://nerd.vasilis.nl/remove-whitespace-inline-block/#comment-197</link>
		<dc:creator>Mathias Bynens</dc:creator>
		<pubDate>Sun, 28 Feb 2010 10:27:40 +0000</pubDate>
		<guid isPermaLink="false">http://nerd.vasilis.nl/?p=126#comment-197</guid>
		<description>I had seen &lt;a href=&quot;http://translate.google.com/translate?&amp;u=http%3A%2F%2Fwww.99css.com%2F%3Ftag%3Dinline-block&amp;sl=zh-CN&amp;tl=en&quot; rel=&quot;nofollow&quot;&gt;some fixes for this behavior&lt;/a&gt; using a negative value for &lt;code&gt;letter-spacing&lt;/code&gt; (again, based on the font used), or by using &lt;code&gt;font-size: 0;&lt;/code&gt; on the wrapper element (&lt;code&gt;UL&lt;/code&gt; in this case) but this is way better. Nice work!

You might want to consider adding &lt;code&gt;&#039;monospace&#039;&lt;/code&gt; to your font declaration, in the rare case neither Courier New nor DejaVu Sans Mono are installed.</description>
		<content:encoded><![CDATA[<p>I had seen <a href="http://translate.google.com/translate?&amp;u=http%3A%2F%2Fwww.99css.com%2F%3Ftag%3Dinline-block&amp;sl=zh-CN&amp;tl=en" rel="nofollow">some fixes for this behavior</a> using a negative value for <code>letter-spacing</code> (again, based on the font used), or by using <code>font-size: 0;</code> on the wrapper element (<code>UL</code> in this case) but this is way better. Nice work!</p>
<p>You might want to consider adding <code>'monospace'</code> to your font declaration, in the rare case neither Courier New nor DejaVu Sans Mono are installed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

