<?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: Negative Proximity</title>
	<atom:link href="http://meyerweb.com/eric/thoughts/2012/03/07/negative-proximity/feed/" rel="self" type="application/rss+xml" />
	<link>http://meyerweb.com/eric/thoughts/2012/03/07/negative-proximity/</link>
	<description>Things that Eric A. Meyer, CSS expert, writes about on his personal Web site; it&#039;s largely Web standards and Web technology, but also various bits of culture, politics, personal observations, and other miscellaneous stuff</description>
	<lastBuildDate>Fri, 10 May 2013 11:50:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Paceaux</title>
		<link>http://meyerweb.com/eric/thoughts/2012/03/07/negative-proximity/#comment-683104</link>
		<dc:creator>Paceaux</dc:creator>
		<pubDate>Tue, 29 May 2012 19:19:41 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1691#comment-683104</guid>
		<description><![CDATA[Thank you for writing this article. I&#039;ve started doing some dev work with the :not() selector and I was incorrectly assuming that it added specificity. Thankfully the scenarios that I had didn&#039;t require an original rule, but it&#039;s good to know that the following two lines have equal specificity. 

.ie #main a{
display:inline;
}
:not(.ie) #main a{
display:inline-block;
}

Why doesn&#039;t &lt;code&gt;:not()&lt;/code&gt; have specificity, then? I can only guess that it&#039;s because there&#039;s an assumption that you don&#039;t have a positive rule that need to be overwritten, right?]]></description>
		<content:encoded><![CDATA[<p>Thank you for writing this article. I&#8217;ve started doing some dev work with the :not() selector and I was incorrectly assuming that it added specificity. Thankfully the scenarios that I had didn&#8217;t require an original rule, but it&#8217;s good to know that the following two lines have equal specificity. </p>
<p>.ie #main a{<br />
display:inline;<br />
}<br />
:not(.ie) #main a{<br />
display:inline-block;<br />
}</p>
<p>Why doesn&#8217;t <code>:not()</code> have specificity, then? I can only guess that it&#8217;s because there&#8217;s an assumption that you don&#8217;t have a positive rule that need to be overwritten, right?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Friday Focus 03/16/12: Wide Slides &#124; Devlounge</title>
		<link>http://meyerweb.com/eric/thoughts/2012/03/07/negative-proximity/#comment-651084</link>
		<dc:creator>Friday Focus 03/16/12: Wide Slides &#124; Devlounge</dc:creator>
		<pubDate>Fri, 16 Mar 2012 13:09:27 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1691#comment-651084</guid>
		<description><![CDATA[[...] &#8211; Negative Proximity &#8220;There’s a subtle aspect of CSS descendant selectors that most people won’t have noticed [...]]]></description>
		<content:encoded><![CDATA[<p>[...] &#8211; Negative Proximity &#8220;There’s a subtle aspect of CSS descendant selectors that most people won’t have noticed [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niels Matthijs</title>
		<link>http://meyerweb.com/eric/thoughts/2012/03/07/negative-proximity/#comment-650412</link>
		<dc:creator>Niels Matthijs</dc:creator>
		<pubDate>Wed, 14 Mar 2012 16:22:28 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1691#comment-650412</guid>
		<description><![CDATA[Nice article! Wrote a very similar one almost two years ago (&lt;a href=&quot;http://www.onderhond.com/blog/onderhond/css-specificity-pt2-lacking%2Bproximity&quot; title=&quot;on css proximity&quot; rel=&quot;nofollow&quot;&gt;css specificity and proximity&lt;/a&gt;) but many people still fail to understand this. Part of the problem is probably that the space operator is equally misunderstood.]]></description>
		<content:encoded><![CDATA[<p>Nice article! Wrote a very similar one almost two years ago (<a href="http://www.onderhond.com/blog/onderhond/css-specificity-pt2-lacking%2Bproximity" title="on css proximity" rel="nofollow">css specificity and proximity</a>) but many people still fail to understand this. Part of the problem is probably that the space operator is equally misunderstood.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Some links for light reading (14/3/12) &#124; Max Design</title>
		<link>http://meyerweb.com/eric/thoughts/2012/03/07/negative-proximity/#comment-650099</link>
		<dc:creator>Some links for light reading (14/3/12) &#124; Max Design</dc:creator>
		<pubDate>Tue, 13 Mar 2012 20:41:15 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1691#comment-650099</guid>
		<description><![CDATA[[...] Negative Proximity [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Negative Proximity [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jftf</title>
		<link>http://meyerweb.com/eric/thoughts/2012/03/07/negative-proximity/#comment-649108</link>
		<dc:creator>jftf</dc:creator>
		<pubDate>Sat, 10 Mar 2012 22:30:49 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1691#comment-649108</guid>
		<description><![CDATA[This is good stuff. Just want to point out that :not is a CSS3 pseudo selector, which isn&#039;t available natively on older browsers, such as IE 7-8. Le sigh.

The good news is that most of us are using a Javascript framework along our CSS! Which means that $(x).not(&#039;.blahClass&#039;) will work across all platforms. Yay.]]></description>
		<content:encoded><![CDATA[<p>This is good stuff. Just want to point out that :not is a CSS3 pseudo selector, which isn&#8217;t available natively on older browsers, such as IE 7-8. Le sigh.</p>
<p>The good news is that most of us are using a Javascript framework along our CSS! Which means that $(x).not(&#8216;.blahClass&#8217;) will work across all platforms. Yay.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephanie Hobson</title>
		<link>http://meyerweb.com/eric/thoughts/2012/03/07/negative-proximity/#comment-648409</link>
		<dc:creator>Stephanie Hobson</dc:creator>
		<pubDate>Thu, 08 Mar 2012 20:14:25 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1691#comment-648409</guid>
		<description><![CDATA[Silly computers doing what we say instead of what we mean.]]></description>
		<content:encoded><![CDATA[<p>Silly computers doing what we say instead of what we mean.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Meyer</title>
		<link>http://meyerweb.com/eric/thoughts/2012/03/07/negative-proximity/#comment-648181</link>
		<dc:creator>Eric Meyer</dc:creator>
		<pubDate>Thu, 08 Mar 2012 01:23:03 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1691#comment-648181</guid>
		<description><![CDATA[Whoops!  Indeed so, &lt;a href=&quot;http://meyerweb.com/eric/thoughts/2012/03/07/negative-proximity/#comment-648132&quot; rel=&quot;nofollow&quot;&gt;Aubrey&lt;/a&gt;.  I’ve corrected the error.  Thanks!]]></description>
		<content:encoded><![CDATA[<p>Whoops!  Indeed so, <a href="http://meyerweb.com/eric/thoughts/2012/03/07/negative-proximity/#comment-648132" rel="nofollow">Aubrey</a>.  I’ve corrected the error.  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aubrey</title>
		<link>http://meyerweb.com/eric/thoughts/2012/03/07/negative-proximity/#comment-648132</link>
		<dc:creator>Aubrey</dc:creator>
		<pubDate>Wed, 07 Mar 2012 21:18:27 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1691#comment-648132</guid>
		<description><![CDATA[Do you mean:

The paragraph is a child of a div that doesn’t have a class of one, but it’s also descended from a DIV that has a class of one. Both rules apply.]]></description>
		<content:encoded><![CDATA[<p>Do you mean:</p>
<p>The paragraph is a child of a div that doesn’t have a class of one, but it’s also descended from a DIV that has a class of one. Both rules apply.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->