<?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: The lost property</title>
	<atom:link href="http://josh.st/2005/05/05/the-lost-property/feed/" rel="self" type="application/rss+xml" />
	<link>http://josh.st/2005/05/05/the-lost-property/</link>
	<description>Web, English, 中国, and various geekosity</description>
	<lastBuildDate>Sat, 05 May 2012 03:55:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Josh</title>
		<link>http://josh.st/2005/05/05/the-lost-property/#comment-3804</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Fri, 06 May 2005 03:48:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.joahua.com/blog/2005/05/05/the-lost-property#comment-3804</guid>
		<description>Yeah, I was actually thinking of pixel positioning (how mezzoblue&#039;s primary nav rollover effect is achieved)... it&#039;s stupidly complicated, I guess, but also potentially very useful.  I&#039;m in the process of making myself understand how it works for a client.</description>
		<content:encoded><![CDATA[<p>Yeah, I was actually thinking of pixel positioning (how mezzoblue’s primary nav rollover effect is achieved)… it’s stupidly complicated, I guess, but also potentially very useful.  I’m in the process of making myself understand how it works for a client.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthom</title>
		<link>http://josh.st/2005/05/05/the-lost-property/#comment-3801</link>
		<dc:creator>Matthom</dc:creator>
		<pubDate>Thu, 05 May 2005 13:27:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.joahua.com/blog/2005/05/05/the-lost-property#comment-3801</guid>
		<description>You talkin&#039; about &lt;code&gt;top left no-repeat&lt;/code&gt; type of thing?

Typically, I declare all the background values with since the solo &lt;code&gt;background&lt;/code&gt; property: 

&lt;code&gt;background: #fff url(/images/bg.big) top left no-repeat;&lt;/code&gt;

I don&#039;t think I&#039;ve ever actually declared &lt;code&gt;background-position&lt;/code&gt; on it&#039;s own.

As far as &quot;seldom used&quot; CSS properties - for me - there&#039;s a fine line between neglecting a property &quot;out of forgetfullness,&quot; and neglecting a property &quot;out of misunderstanding.&quot;

In other words, I don&#039;t use some properties because some are a little more tricky than others.

Such as &lt;code&gt;clear&lt;/code&gt;.

All in all, I have to say I don&#039;t use &lt;code&gt;display&lt;/code&gt; as often as I would like.</description>
		<content:encoded><![CDATA[<p>You talkin’ about <code>top left no-repeat</code> type of thing?</p>
<p>Typically, I declare all the background values with since the solo <code>background</code> property: </p>
<p><code>background: #fff url(/images/bg.big) top left no-repeat;</code></p>
<p>I don’t think I’ve ever actually declared <code>background-position</code> on it’s own.</p>
<p>As far as “seldom used” CSS properties — for me — there’s a fine line between neglecting a property “out of forgetfullness,” and neglecting a property “out of misunderstanding.”</p>
<p>In other words, I don’t use some properties because some are a little more tricky than others.</p>
<p>Such as <code>clear</code>.</p>
<p>All in all, I have to say I don’t use <code>display</code> as often as I would like.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced

Served from: josh.st @ 2012-05-22 09:06:13 -->
