<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Clientcide (Formerly CNET's Clientside) &#187; Browser Stuff</title>
	<atom:link href="http://www.clientcide.com/category/best-practices/browser-issues/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.clientcide.com</link>
	<description>Making stuff work on the other side of the request.</description>
	<lastBuildDate>Fri, 06 Jan 2012 17:03:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>CNET API uses: New Facebook Application</title>
		<link>http://www.clientcide.com/uncategorized/cnet-api-uses-new-facebook-application/</link>
		<comments>http://www.clientcide.com/uncategorized/cnet-api-uses-new-facebook-application/#comments</comments>
		<pubDate>Tue, 26 Jun 2007 21:29:35 +0000</pubDate>
		<dc:creator>Hamm</dc:creator>
				<category><![CDATA[Browser Stuff]]></category>
		<category><![CDATA[CNET API]]></category>
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/uncategorized/cnet-api-uses-new-facebook-application/</guid>
		<description><![CDATA[There is a new &#8220;Facebook&#8221; application that utilizes CNETs great API system. This app that was developed is called &#8220;My Tech&#8221;.
Apart from the great technology use, it is a fun way to show off your latest tech gear to your friends. The best part is you can show your disdain for certain tech products if [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/uncategorized/cnet-api-uses-new-facebook-application/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Back Button Support: Safari and Speed</title>
		<link>http://www.clientcide.com/best-practices/browser-issues/back-button-support-safari-and-speed/</link>
		<comments>http://www.clientcide.com/best-practices/browser-issues/back-button-support-safari-and-speed/#comments</comments>
		<pubDate>Thu, 16 Nov 2006 17:53:52 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Ajax]]></category>
		<category><![CDATA[Browser Stuff]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/best-practices/browser-issues/back-button-support-safari-and-speed/</guid>
		<description><![CDATA[via Ajaxian:
Daniel Kantor has implemented a Back button solution in Streampad and has shared it with us.
One of the main gripes against AJAX webapps is how they break the back button in a typical browser. There have been a few solutions (notably Brad Neubergâ€™s Really Simple History) but none have got it working in Safari. [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/best-practices/browser-issues/back-button-support-safari-and-speed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IE7: Twice as performant as IE6, but half as slow as FF 1.5</title>
		<link>http://www.clientcide.com/best-practices/browser-issues/ie7-twice-as-performant-as-ie6-but-half-as-slow-as-ff-15/</link>
		<comments>http://www.clientcide.com/best-practices/browser-issues/ie7-twice-as-performant-as-ie6-but-half-as-slow-as-ff-15/#comments</comments>
		<pubDate>Thu, 26 Oct 2006 20:19:27 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Browser Stuff]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/best-practices/browser-issues/ie7-twice-as-performant-as-ie6-but-half-as-slow-as-ff-15/</guid>
		<description><![CDATA[via ajaxian: IE7: Twice as performant as IE6, but half as slow as FF 1.5
Ross Dargahi of Zimbra complained about IE 6 performance.  Since IE 7 is here, he decided to retry his tests and see how Microsoft had done:
Microsoft&#8217;s IE team has clearly been hard at work on improving their browser&#8217;s memory management [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/best-practices/browser-issues/ie7-twice-as-performant-as-ie6-but-half-as-slow-as-ff-15/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Detecting IE7+ in javascript</title>
		<link>http://www.clientcide.com/best-practices/browser-issues/detecting-ie7-in-javascript/</link>
		<comments>http://www.clientcide.com/best-practices/browser-issues/detecting-ie7-in-javascript/#comments</comments>
		<pubDate>Thu, 26 Oct 2006 19:38:18 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Browser Stuff]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/best-practices/browser-issues/detecting-ie7-in-javascript/</guid>
		<description><![CDATA[via ajaxian:
Abe Fettig knows that we need to start detecting the difference between IE6- and IE7+, because a lot of the hacks that we were using for IE are no longer needed.
He didn&#8217;t want to grok the user agent, as that is very brittle, so he came up with:


if (typeof document.body.style.maxHeight != &#8220;undefined&#8221;) {
// IE [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/best-practices/browser-issues/detecting-ie7-in-javascript/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IE-7 standalone (and, for that matter, IE 3, 4, 5, and 6)</title>
		<link>http://www.clientcide.com/tools/ie-7-standalone-and-for-that-matter-ie-3-4-5-and-6/</link>
		<comments>http://www.clientcide.com/tools/ie-7-standalone-and-for-that-matter-ie-3-4-5-and-6/#comments</comments>
		<pubDate>Thu, 26 Oct 2006 18:52:04 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Browser Stuff]]></category>
		<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/tools/ie-7-standalone-and-for-that-matter-ie-3-4-5-and-6/</guid>
		<description><![CDATA[Want several copies of IE running side by side? Want to test out IE 7 but don&#8217;t really want to zorch your IE 6 that you also need to test? No problem.
]]></description>
		<wfw:commentRss>http://www.clientcide.com/tools/ie-7-standalone-and-for-that-matter-ie-3-4-5-and-6/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Screencast on Diagnosing Memory Leaks in IE</title>
		<link>http://www.clientcide.com/best-practices/browser-issues/screencast-on-diagnosing-memory-leaks-in-ie/</link>
		<comments>http://www.clientcide.com/best-practices/browser-issues/screencast-on-diagnosing-memory-leaks-in-ie/#comments</comments>
		<pubDate>Fri, 31 Mar 2006 18:54:47 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Browser Stuff]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=63</guid>
		<description><![CDATA[via Ajaxian:
Patrick Fitzgerald posted a nice screencast explaining how he diagnosed and fixed an IE memory leak in his tabifier library.  He walks through using the free tool Process Explorer to watch IE&#8217;s memory grow with each page refresh.  He writes:
This screencast discusses how I diagnosed and fixed a memory leak in a [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/best-practices/browser-issues/screencast-on-diagnosing-memory-leaks-in-ie/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>window.onload and its issues</title>
		<link>http://www.clientcide.com/best-practices/organizing-code/windowonload-and-its-issues/</link>
		<comments>http://www.clientcide.com/best-practices/organizing-code/windowonload-and-its-issues/#comments</comments>
		<pubDate>Tue, 21 Feb 2006 19:27:53 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Browser Stuff]]></category>
		<category><![CDATA[Event Scripting]]></category>
		<category><![CDATA[Examples]]></category>
		<category><![CDATA[Organizing Code]]></category>
		<category><![CDATA[Reference]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=42</guid>
		<description><![CDATA[Bill Graham was asking me about where to put javascript events today. window.onload? At the bottom of the html document? Attached to the onload event of an image somewhere in the page?
Here&#8217;s an article by Dean Edwards on an interesting solution that works for IE and Firefox.
For the life of me, I can&#8217;t find the [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/best-practices/organizing-code/windowonload-and-its-issues/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Yahoo&#8217;s &#8220;Graded Browser Support&#8221;</title>
		<link>http://www.clientcide.com/best-practices/yahoos-graded-browser-support/</link>
		<comments>http://www.clientcide.com/best-practices/yahoos-graded-browser-support/#comments</comments>
		<pubDate>Tue, 14 Feb 2006 18:48:11 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Browser Stuff]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=23</guid>
		<description><![CDATA[Part of Yahoo&#8217;s library release includes their browser support ethos. It&#8217;s worth a read.


Graded Browser Support
By Nate Koechley
Senior Web Developer
Yahoo! Inc.
February 13, 2006
In the first 10 years of professional web development, back in the early &#8217;90s, browser support was binary: Do you or don&#8217;t you support a given browser? When the answer was &#8216;No&#8217;, user [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/best-practices/yahoos-graded-browser-support/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

