<?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: For the Developers in the Audience, a Scary Quote</title>
	<atom:link href="http://www.drunkenfist.com/304/2008/06/03/for-the-developers-in-the-audience-a-scary-quote/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.drunkenfist.com/304/2008/06/03/for-the-developers-in-the-audience-a-scary-quote/</link>
	<description>Rob Larsen writes on web design and development, entertainment, sports and culture.</description>
	<pubDate>Fri, 09 Jan 2009 05:48:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ryan</title>
		<link>http://www.drunkenfist.com/304/2008/06/03/for-the-developers-in-the-audience-a-scary-quote/comment-page-1/#comment-16569</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Wed, 04 Jun 2008 14:45:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.drunkenfist.com/304/?p=4599#comment-16569</guid>
		<description>Firebug had an issue with displaying anchor styles in Firefox 2.0.0.12 (and it didn't matter how deep they were nested).  Thankfully this has been fixed.</description>
		<content:encoded><![CDATA[<p>Firebug had an issue with displaying anchor styles in Firefox 2.0.0.12 (and it didn't matter how deep they were nested).  Thankfully this has been fixed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rob</title>
		<link>http://www.drunkenfist.com/304/2008/06/03/for-the-developers-in-the-audience-a-scary-quote/comment-page-1/#comment-16568</link>
		<dc:creator>rob</dc:creator>
		<pubDate>Wed, 04 Jun 2008 00:58:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.drunkenfist.com/304/?p=4599#comment-16568</guid>
		<description>Thanks for clarifying. I'll keep my eyes peeled. 

I'm also going to experiment a little bit with some of my sites to see if I can find an example where it breaks. 

Curiosity has me.</description>
		<content:encoded><![CDATA[<p>Thanks for clarifying. I'll keep my eyes peeled. </p>
<p>I'm also going to experiment a little bit with some of my sites to see if I can find an example where it breaks. </p>
<p>Curiosity has me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave S.</title>
		<link>http://www.drunkenfist.com/304/2008/06/03/for-the-developers-in-the-audience-a-scary-quote/comment-page-1/#comment-16567</link>
		<dc:creator>Dave S.</dc:creator>
		<pubDate>Wed, 04 Jun 2008 00:06:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.drunkenfist.com/304/?p=4599#comment-16567</guid>
		<description>Of course, now I can't find an instance to call out as an example, but I can describe the symptoms. 

I've also noticed on a few recent projects other than this one that the inspector breaks down for deeply-nested elements. I'm thinking a dozen or so levels deep, something like anchors within list items within uls within list items within a second set of uls within multiple divs etc.

When using either the 'inspect' button, or clicking on the element in the source listing, the CSS inspector stops showing the calculated style for that element. I generally can get the parent's style in those cases, but some elements just stop reporting properly.

Wish I could replicate it at the moment, but you've given me something to document next time I run across it.</description>
		<content:encoded><![CDATA[<p>Of course, now I can't find an instance to call out as an example, but I can describe the symptoms. </p>
<p>I've also noticed on a few recent projects other than this one that the inspector breaks down for deeply-nested elements. I'm thinking a dozen or so levels deep, something like anchors within list items within uls within list items within a second set of uls within multiple divs etc.</p>
<p>When using either the 'inspect' button, or clicking on the element in the source listing, the CSS inspector stops showing the calculated style for that element. I generally can get the parent's style in those cases, but some elements just stop reporting properly.</p>
<p>Wish I could replicate it at the moment, but you've given me something to document next time I run across it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
