<?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 for Web 3.0, 6 Bladed Razors, 7 Minute Abs</title>
	<atom:link href="http://www.zachleat.com/web/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zachleat.com/web</link>
	<description></description>
	<lastBuildDate>Fri, 12 Mar 2010 20:47:15 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Dear IE6: Please Cache my Images. by Über 20 Tipps zum Internet Explorer 6 &#8211; Meinem besten Freund &#124; Thomas Horster</title>
		<link>http://www.zachleat.com/web/2008/10/18/dear-ie6-please-cache-my-images/comment-page-1/#comment-1925</link>
		<dc:creator>Über 20 Tipps zum Internet Explorer 6 &#8211; Meinem besten Freund &#124; Thomas Horster</dc:creator>
		<pubDate>Fri, 12 Mar 2010 20:47:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=149#comment-1925</guid>
		<description>[...] mit den diversen Internetexplorernder beste PNG-Fix für Transparenzen in pngs (meiner Meinung nach)Wie verhindere ich zusätzliche requests im IE6 bei mehrfach verwendeten Bildern?den IE6 zum IE7 oder IE8 machen (na ja, in etwa &#8230;)Ja, mein alter Freund, was werden wir ohne [...]</description>
		<content:encoded><![CDATA[<p>[...] mit den diversen Internetexplorernder beste PNG-Fix für Transparenzen in pngs (meiner Meinung nach)Wie verhindere ich zusätzliche requests im IE6 bei mehrfach verwendeten Bildern?den IE6 zum IE7 oder IE8 machen (na ja, in etwa &#8230;)Ja, mein alter Freund, was werden wir ohne [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using Phing to automate JavaScript and CSS Minimization by Tristan Eastburn</title>
		<link>http://www.zachleat.com/web/2007/08/11/using-phing-to-automate-javascript-and-css-minimization/comment-page-1/#comment-1908</link>
		<dc:creator>Tristan Eastburn</dc:creator>
		<pubDate>Fri, 05 Mar 2010 00:28:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/2007/08/11/using-phing-to-automate-javascript-and-css-minimization/#comment-1908</guid>
		<description>OK I spoke a little soon :)

Line 216 (preserveCss) also need the fix from the above comment.

Also, properties with number values, i.e. lines 199, 203 and 209 (optimizeShortand, propertyCase and mergeSelectors) need to be changed from:
if(!empty($this-&gt;propertyName))

to:
if(isset($this-&gt;propertyName))

since they all have number values, empty() will fail for their 0 value.</description>
		<content:encoded><![CDATA[<p>OK I spoke a little soon :)</p>
<p>Line 216 (preserveCss) also need the fix from the above comment.</p>
<p>Also, properties with number values, i.e. lines 199, 203 and 209 (optimizeShortand, propertyCase and mergeSelectors) need to be changed from:<br />
if(!empty($this-&gt;propertyName))</p>
<p>to:<br />
if(isset($this-&gt;propertyName))</p>
<p>since they all have number values, empty() will fail for their 0 value.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using Phing to automate JavaScript and CSS Minimization by Tristan Eastburn</title>
		<link>http://www.zachleat.com/web/2007/08/11/using-phing-to-automate-javascript-and-css-minimization/comment-page-1/#comment-1907</link>
		<dc:creator>Tristan Eastburn</dc:creator>
		<pubDate>Thu, 04 Mar 2010 23:29:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/2007/08/11/using-phing-to-automate-javascript-and-css-minimization/#comment-1907</guid>
		<description>Thanks a lot for these filters! They work quite well so far and saved me a lot of time.

I know you wrote this article 2.5 years ago, but I ran across a tiny bug with in the CssTidyFilter where the &quot;remove_last_;&quot; property doesn&#039;t get set properly, though. The bug appears for me with Phing 2.4.0 and CssTidy 1.3 on Ubuntu 9.10 Karmic, haven&#039;t tested other versions.

My build file has this line:
$lt;param name=&quot;remove_last_;&quot; value=&quot;true&quot;/&gt;

And putting an echo in CssTidyFilter after calling getParam() shows that somewhere along the way it gets changed:
var_dump($this-&gt;removeLastSemicolon) = string(1) &quot;1&quot;

So the following assignment fails:
$css-&gt;set_cfg(&#039;remove_last_;&#039;,$this-&gt;removeLastSemicolon==&#039;true&#039;?true:false);

I will send a patch to the author, but in case he can&#039;t get to it or no longer maintains this project, you can just do this (around line 202):
$css-&gt;set_cfg(&#039;remove_last_;&#039;,!empty($this-&gt;removeLastSemicolon)?true:false);

This fix may or may not work for other properties, I have not tried it. The other properties I use (&#039;merge_selectors&#039;, &#039;template&#039; and &#039;preserveCss&#039;) seem to work fine.

Another suggested change would be to use &quot;require_once()&quot; instead of &quot;include_once()&quot; as the script should fail if it can&#039;t find the files it depends on.</description>
		<content:encoded><![CDATA[<p>Thanks a lot for these filters! They work quite well so far and saved me a lot of time.</p>
<p>I know you wrote this article 2.5 years ago, but I ran across a tiny bug with in the CssTidyFilter where the &#8220;remove_last_;&#8221; property doesn&#8217;t get set properly, though. The bug appears for me with Phing 2.4.0 and CssTidy 1.3 on Ubuntu 9.10 Karmic, haven&#8217;t tested other versions.</p>
<p>My build file has this line:<br />
$lt;param name=&#8221;remove_last_;&#8221; value=&#8221;true&#8221;/&gt;</p>
<p>And putting an echo in CssTidyFilter after calling getParam() shows that somewhere along the way it gets changed:<br />
var_dump($this-&gt;removeLastSemicolon) = string(1) &#8220;1&#8243;</p>
<p>So the following assignment fails:<br />
$css-&gt;set_cfg(&#8216;remove_last_;&#8217;,$this-&gt;removeLastSemicolon==&#8217;true&#8217;?true:false);</p>
<p>I will send a patch to the author, but in case he can&#8217;t get to it or no longer maintains this project, you can just do this (around line 202):<br />
$css-&gt;set_cfg(&#8216;remove_last_;&#8217;,!empty($this-&gt;removeLastSemicolon)?true:false);</p>
<p>This fix may or may not work for other properties, I have not tried it. The other properties I use (&#8216;merge_selectors&#8217;, &#8216;template&#8217; and &#8216;preserveCss&#8217;) seem to work fine.</p>
<p>Another suggested change would be to use &#8220;require_once()&#8221; instead of &#8220;include_once()&#8221; as the script should fail if it can&#8217;t find the files it depends on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Internet Explorer Array.sort Unreliable by Какво ново в последната седмица на Февуари &#124; NeXt</title>
		<link>http://www.zachleat.com/web/2010/02/24/array-sort/comment-page-1/#comment-1899</link>
		<dc:creator>Какво ново в последната седмица на Февуари &#124; NeXt</dc:creator>
		<pubDate>Sun, 28 Feb 2010 12:50:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=568#comment-1899</guid>
		<description>[...] Internet Explorer Array.sort Unreliable &#8211; като стана дума за лоши технологии, IE има проблем с Array.sort. [...]</description>
		<content:encoded><![CDATA[<p>[...] Internet Explorer Array.sort Unreliable &#8211; като стана дума за лоши технологии, IE има проблем с Array.sort. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Internet Explorer Array.sort Unreliable by Zach Leatherman</title>
		<link>http://www.zachleat.com/web/2010/02/24/array-sort/comment-page-1/#comment-1885</link>
		<dc:creator>Zach Leatherman</dc:creator>
		<pubDate>Thu, 25 Feb 2010 05:23:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=568#comment-1885</guid>
		<description>I don&#039;t see why they wouldn&#039;t incorporate it, since it is introducing bugs in all versions of Internet Explorer.  We&#039;ll see how your report pans out.  I&#039;ve submitted a bug before to the Closure Compiler team and it was fixed right away.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t see why they wouldn&#8217;t incorporate it, since it is introducing bugs in all versions of Internet Explorer.  We&#8217;ll see how your report pans out.  I&#8217;ve submitted a bug before to the Closure Compiler team and it was fixed right away.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Internet Explorer Array.sort Unreliable by ishtar</title>
		<link>http://www.zachleat.com/web/2010/02/24/array-sort/comment-page-1/#comment-1884</link>
		<dc:creator>ishtar</dc:creator>
		<pubDate>Thu, 25 Feb 2010 03:29:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=568#comment-1884</guid>
		<description>Nice write-up. I wonder if your suggestion can be incorporated into the compiled code Google Closure compiler outputs. I noticed that the same solution (of not reassigning the argument variables) fixes the issue in IE for the problem that led me to post that ticket.</description>
		<content:encoded><![CDATA[<p>Nice write-up. I wonder if your suggestion can be incorporated into the compiled code Google Closure compiler outputs. I noticed that the same solution (of not reassigning the argument variables) fixes the issue in IE for the problem that led me to post that ticket.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on If the Menu Fitts, We Must Acquit by Zach Leatherman</title>
		<link>http://www.zachleat.com/web/2010/02/15/if-the-menu-fitts-we-must-acquit/comment-page-1/#comment-1880</link>
		<dc:creator>Zach Leatherman</dc:creator>
		<pubDate>Fri, 19 Feb 2010 23:30:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=542#comment-1880</guid>
		<description>Thanks guys.

Also, another thought: the &quot;infinite edge&quot; case doesn&#039;t quite apply for touchscreen interfaces.</description>
		<content:encoded><![CDATA[<p>Thanks guys.</p>
<p>Also, another thought: the &#8220;infinite edge&#8221; case doesn&#8217;t quite apply for touchscreen interfaces.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PHP Pretty Date by Jelle</title>
		<link>http://www.zachleat.com/web/2008/02/10/php-pretty-date/comment-page-1/#comment-1878</link>
		<dc:creator>Jelle</dc:creator>
		<pubDate>Thu, 18 Feb 2010 11:29:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/2008/02/10/php-pretty-date/#comment-1878</guid>
		<description>Support for future!

&lt;code&gt;

= 5.1 by Zach Leatherman (zachleat.com) 
// Slight modification denoted below to handle months and years. 
class prettydate 
{ 
    public static function getStringResolved($date, $compareTo = NULL) 
    { 
        if(!is_null($compareTo)) { 
            $compareTo = new DateTime($compareTo); 
        } 
        return self::getString(new DateTime($date), $compareTo); 
    } 

    public static function getString(DateTime $date, DateTime $compareTo = NULL) 
    { 
        if(is_null($compareTo)) { 
            $compareTo = new DateTime(&#039;now&#039;); 
        } 
        $diff = $compareTo-&gt;format(&#039;U&#039;) - $date-&gt;format(&#039;U&#039;); 
        $dayDiff = floor($diff / 86400); 
		
		if(is_nan($dayDiff)) return &#039;&#039;; 
		
		$end = &#039;ago&#039;;
		if($dayDiff &lt; 0) {	# date is in the future
			$end = &#039;left&#039;;
			$dayDiff *= -1;
		}

        if($dayDiff == 0) { 
            if($diff &lt; 60) { 
                return &#039;Just now&#039;; 
            } elseif($diff &lt; 120) { 
                return &#039;1 minute &#039;.$end; 
            } elseif($diff &lt; 3600) { 
                return floor($diff/60) . &#039; minutes &#039;.$end; 
            } elseif($diff &lt; 7200) { 
                return &#039;1 hour &#039;.$end; 
            } elseif($diff &lt; 86400) { 
                return floor($diff/3600) . &#039; hours &#039;.$end; 
            } 
        } elseif($dayDiff == 1) { 
            return &#039;Yesterday&#039;; 
        } elseif($dayDiff &lt; 7) { 
            return $dayDiff . &#039; days &#039;.$end; 
        } elseif($dayDiff == 7) { 
            return &#039;1 week &#039;.$end; 
        } elseif($dayDiff &lt; (7*6)) { // Modifications Start Here 
            // 6 weeks at most 
            return ceil($dayDiff/7) . &#039; weeks &#039;.$end; 
        } elseif($dayDiff &lt; 365) { 
            return ceil($dayDiff/(365/12)) . &#039; months &#039;.$end; 
        } else { 
            $years = round($dayDiff/365); 
            return $years . &#039; year&#039; . ($years != 1 ? &#039;s&#039; : &#039;&#039;) . &#039; &#039;.$end; 
        } 
    } 
}

&lt;code&gt;</description>
		<content:encoded><![CDATA[<p>Support for future!</p>
<p><code></p>
<p>= 5.1 by Zach Leatherman (zachleat.com)<br />
// Slight modification denoted below to handle months and years.<br />
class prettydate<br />
{<br />
    public static function getStringResolved($date, $compareTo = NULL)<br />
    {<br />
        if(!is_null($compareTo)) {<br />
            $compareTo = new DateTime($compareTo);<br />
        }<br />
        return self::getString(new DateTime($date), $compareTo);<br />
    } </p>
<p>    public static function getString(DateTime $date, DateTime $compareTo = NULL)<br />
    {<br />
        if(is_null($compareTo)) {<br />
            $compareTo = new DateTime('now');<br />
        }<br />
        $diff = $compareTo-&gt;format('U') - $date-&gt;format('U');<br />
        $dayDiff = floor($diff / 86400); </p>
<p>		if(is_nan($dayDiff)) return ''; </p>
<p>		$end = 'ago';<br />
		if($dayDiff &lt; 0) {	# date is in the future<br />
			$end = &#039;left&#039;;<br />
			$dayDiff *= -1;<br />
		}</p>
<p>        if($dayDiff == 0) {<br />
            if($diff &lt; 60) {<br />
                return &#039;Just now&#039;;<br />
            } elseif($diff &lt; 120) {<br />
                return &#039;1 minute &#039;.$end;<br />
            } elseif($diff &lt; 3600) {<br />
                return floor($diff/60) . &#039; minutes &#039;.$end;<br />
            } elseif($diff &lt; 7200) {<br />
                return &#039;1 hour &#039;.$end;<br />
            } elseif($diff &lt; 86400) {<br />
                return floor($diff/3600) . &#039; hours &#039;.$end;<br />
            }<br />
        } elseif($dayDiff == 1) {<br />
            return &#039;Yesterday&#039;;<br />
        } elseif($dayDiff &lt; 7) {<br />
            return $dayDiff . &#039; days &#039;.$end;<br />
        } elseif($dayDiff == 7) {<br />
            return &#039;1 week &#039;.$end;<br />
        } elseif($dayDiff &lt; (7*6)) { // Modifications Start Here<br />
            // 6 weeks at most<br />
            return ceil($dayDiff/7) . &#039; weeks &#039;.$end;<br />
        } elseif($dayDiff &lt; 365) {<br />
            return ceil($dayDiff/(365/12)) . &#039; months &#039;.$end;<br />
        } else {<br />
            $years = round($dayDiff/365);<br />
            return $years . &#039; year&#039; . ($years != 1 ? &#039;s&#039; : &#039;&#039;) . &#039; &#039;.$end;<br />
        }<br />
    }<br />
}</p>
<p></code><code></code></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on If the Menu Fitts, We Must Acquit by Daniel Shaw</title>
		<link>http://www.zachleat.com/web/2010/02/15/if-the-menu-fitts-we-must-acquit/comment-page-1/#comment-1875</link>
		<dc:creator>Daniel Shaw</dc:creator>
		<pubDate>Wed, 17 Feb 2010 16:39:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=542#comment-1875</guid>
		<description>Great post Zach. Very interesting observations.

I have two monitors and have one to the left of my main browsing window. Interesting how that infinite edge disappears when I have to consciously stop in that space.</description>
		<content:encoded><![CDATA[<p>Great post Zach. Very interesting observations.</p>
<p>I have two monitors and have one to the left of my main browsing window. Interesting how that infinite edge disappears when I have to consciously stop in that space.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on If the Menu Fitts, We Must Acquit by Jordan</title>
		<link>http://www.zachleat.com/web/2010/02/15/if-the-menu-fitts-we-must-acquit/comment-page-1/#comment-1873</link>
		<dc:creator>Jordan</dc:creator>
		<pubDate>Wed, 17 Feb 2010 16:14:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=542#comment-1873</guid>
		<description>IE8 (fullscreen mode) on Win7/Server 2008 R2 works on both cases (disabling the status bar).
Chromium (fullscreen mode) on Win7/Server 2008 R2 said some mean words and didn&#039;t work in either case.

After I went and did this I saw that you noted the fullscreen mode was out of scope, but I thought I&#039;d let you know the results anyway.

Thanks for the write-up. It&#039;s a very interesting thought - definitely something to consider when designing navigation. Multi-monitor situations are another interesting case for this, but I&#039;m guessing isn&#039;t common enough to stress over.</description>
		<content:encoded><![CDATA[<p>IE8 (fullscreen mode) on Win7/Server 2008 R2 works on both cases (disabling the status bar).<br />
Chromium (fullscreen mode) on Win7/Server 2008 R2 said some mean words and didn&#8217;t work in either case.</p>
<p>After I went and did this I saw that you noted the fullscreen mode was out of scope, but I thought I&#8217;d let you know the results anyway.</p>
<p>Thanks for the write-up. It&#8217;s a very interesting thought &#8211; definitely something to consider when designing navigation. Multi-monitor situations are another interesting case for this, but I&#8217;m guessing isn&#8217;t common enough to stress over.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on If the Menu Fitts, We Must Acquit by James Padolsey</title>
		<link>http://www.zachleat.com/web/2010/02/15/if-the-menu-fitts-we-must-acquit/comment-page-1/#comment-1872</link>
		<dc:creator>James Padolsey</dc:creator>
		<pubDate>Tue, 16 Feb 2010 18:01:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=542#comment-1872</guid>
		<description>Great post Zach! And an excellent point!

FWIW, Opera (I tested v. 10) seems to be compatible with this &quot;law&quot; too.</description>
		<content:encoded><![CDATA[<p>Great post Zach! And an excellent point!</p>
<p>FWIW, Opera (I tested v. 10) seems to be compatible with this &#8220;law&#8221; too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Trash that &#8220;Back to Top&#8221; Link by Jordan</title>
		<link>http://www.zachleat.com/web/2010/02/05/trash-that-back-to-top-link/comment-page-1/#comment-1867</link>
		<dc:creator>Jordan</dc:creator>
		<pubDate>Tue, 09 Feb 2010 21:00:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=376#comment-1867</guid>
		<description>Is it ironic, then, that I read this article through Feedly, which has a &quot;back to top&quot; link at the bottom? I&#039;ve often wondered if the link itself has &lt;em&gt;ever&lt;/em&gt; been useful, considering the Home key on the keyboard exists.

I&#039;m probably the only one that uses it.</description>
		<content:encoded><![CDATA[<p>Is it ironic, then, that I read this article through Feedly, which has a &#8220;back to top&#8221; link at the bottom? I&#8217;ve often wondered if the link itself has <em>ever</em> been useful, considering the Home key on the keyboard exists.</p>
<p>I&#8217;m probably the only one that uses it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on JavaScript Code Coverage Tool for Firebug by 10 Useful Firefox Extensions to Supercharge Firebug - AjaxJ.F &#124; ZendFramework &#124; Codeigniter &#124; Jquery &#124; Ajax</title>
		<link>http://www.zachleat.com/web/2007/04/18/javascript-code-coverage-tool-for-firebug/comment-page-1/#comment-1865</link>
		<dc:creator>10 Useful Firefox Extensions to Supercharge Firebug - AjaxJ.F &#124; ZendFramework &#124; Codeigniter &#124; Jquery &#124; Ajax</dc:creator>
		<pubDate>Sat, 06 Feb 2010 16:08:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/2007/04/18/javascript-code-coverage-tool-for-firebug/#comment-1865</guid>
		<description>[...] 7. FirebugCodeCoverage [...]</description>
		<content:encoded><![CDATA[<p>[...] 7. FirebugCodeCoverage [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The &#8220;24&#8243; Clock on ALARMd by Zach Leatherman</title>
		<link>http://www.zachleat.com/web/2010/01/24/the-24-clock-on-alarmd/comment-page-1/#comment-1862</link>
		<dc:creator>Zach Leatherman</dc:creator>
		<pubDate>Sat, 30 Jan 2010 15:09:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=465#comment-1862</guid>
		<description>It&#039;s HTML 5 and doesn&#039;t use Flash!  Fully compatible with the iPad and multi-touch!</description>
		<content:encoded><![CDATA[<p>It&#8217;s HTML 5 and doesn&#8217;t use Flash!  Fully compatible with the iPad and multi-touch!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The &#8220;24&#8243; Clock on ALARMd by Jonathan Sharp</title>
		<link>http://www.zachleat.com/web/2010/01/24/the-24-clock-on-alarmd/comment-page-1/#comment-1858</link>
		<dc:creator>Jonathan Sharp</dc:creator>
		<pubDate>Wed, 27 Jan 2010 22:16:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=465#comment-1858</guid>
		<description>Is it Web 2.0 compatible with AJAX? Oh, and what port do you need to open to send it to my screen?</description>
		<content:encoded><![CDATA[<p>Is it Web 2.0 compatible with AJAX? Oh, and what port do you need to open to send it to my screen?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The &#8220;24&#8243; Clock on ALARMd by Matt Steele</title>
		<link>http://www.zachleat.com/web/2010/01/24/the-24-clock-on-alarmd/comment-page-1/#comment-1846</link>
		<dc:creator>Matt Steele</dc:creator>
		<pubDate>Sun, 24 Jan 2010 19:54:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=465#comment-1846</guid>
		<description>A few suggestions:
Put the clock tick sound on the page
Make the default video Jack Bauer yelling Damnit!
Stop using sensible technical phrases and start uttering gibberish.</description>
		<content:encoded><![CDATA[<p>A few suggestions:<br />
Put the clock tick sound on the page<br />
Make the default video Jack Bauer yelling Damnit!<br />
Stop using sensible technical phrases and start uttering gibberish.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DIY Webdings &#8211; CSS Sprites using @font-face by The &#8220;24&#8243; Clock on ALARMd</title>
		<link>http://www.zachleat.com/web/2010/01/03/css-sprites-using-font-face/comment-page-1/#comment-1843</link>
		<dc:creator>The &#8220;24&#8243; Clock on ALARMd</dc:creator>
		<pubDate>Sun, 24 Jan 2010 07:37:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=433#comment-1843</guid>
		<description>[...] Subscribe  Follow  Tournology    Skip to content AboutAbout Zach LeathermanProjects       &#171; DIY Webdings &#8211; CSS Sprites using @font-face [...]</description>
		<content:encoded><![CDATA[<p>[...] Subscribe  Follow  Tournology    Skip to content AboutAbout Zach LeathermanProjects       &laquo; DIY Webdings &#8211; CSS Sprites using @font-face [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Performance Caveat with jQuery Selectors and Live Events by On jQuery&#39;s live() &#171; Paul Irish</title>
		<link>http://www.zachleat.com/web/2009/05/08/performance-caveat-with-jquery-selectors-and-live-events/comment-page-1/#comment-1839</link>
		<dc:creator>On jQuery&#39;s live() &#171; Paul Irish</dc:creator>
		<pubDate>Fri, 22 Jan 2010 18:00:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=211#comment-1839</guid>
		<description>[...] uses the jQobj.selector property and context. It&#039;s a waste, I agree. But you can avoid it. Zachleat posted this technique first. Then I stole a code snippet from @janl to show off in my jQuery Performance talk for jQCon. [...]</description>
		<content:encoded><![CDATA[<p>[...] uses the jQobj.selector property and context. It&#39;s a waste, I agree. But you can avoid it. Zachleat posted this technique first. Then I stole a code snippet from @janl to show off in my jQuery Performance talk for jQCon. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Performance Caveat with jQuery Selectors and Live Events by Performant .live() in jQuery 1.4 at don&#8217;t explain</title>
		<link>http://www.zachleat.com/web/2009/05/08/performance-caveat-with-jquery-selectors-and-live-events/comment-page-1/#comment-1832</link>
		<dc:creator>Performant .live() in jQuery 1.4 at don&#8217;t explain</dc:creator>
		<pubDate>Thu, 21 Jan 2010 09:00:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=211#comment-1832</guid>
		<description>[...] significant optimization I&#8217;ve been using with jQuery 1.3.2 for some time now was documented by Zach Leatherman — when you use .live() (and if you have a dynamic number of elements you should always be using [...]</description>
		<content:encoded><![CDATA[<p>[...] significant optimization I&#8217;ve been using with jQuery 1.3.2 for some time now was documented by Zach Leatherman — when you use .live() (and if you have a dynamic number of elements you should always be using [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Performance Caveat with jQuery Selectors and Live Events by links for 2010-01-20 &#171; BarelyBlogging</title>
		<link>http://www.zachleat.com/web/2009/05/08/performance-caveat-with-jquery-selectors-and-live-events/comment-page-1/#comment-1830</link>
		<dc:creator>links for 2010-01-20 &#171; BarelyBlogging</dc:creator>
		<pubDate>Thu, 21 Jan 2010 00:33:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=211#comment-1830</guid>
		<description>[...] Performance Caveat with jQuery Selectors and Live Events (tags: jquery live) [...]</description>
		<content:encoded><![CDATA[<p>[...] Performance Caveat with jQuery Selectors and Live Events (tags: jquery live) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
