<?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 Bugs</title>
	<atom:link href="http://www.clientcide.com/category/browser-bugs/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>Dragging and IE7</title>
		<link>http://www.clientcide.com/browser-bugs/dragging-and-ie7/</link>
		<comments>http://www.clientcide.com/browser-bugs/dragging-and-ie7/#comments</comments>
		<pubDate>Wed, 10 Dec 2008 22:30:31 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Browser Bugs]]></category>

		<guid isPermaLink="false">http://www.clientcide.com/?p=593</guid>
		<description><![CDATA[So I got an email today from someone having issues with dragging things in IE7. They even hit my example in the wikitorial for resizing things and reproduced their trouble. The issue showed up as they tried to drag the handle. Nothing happened until they released (mouseup) the handle and then the object followed the [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/browser-bugs/dragging-and-ie7/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>MSFT Fixes Memory Leaks in IE6</title>
		<link>http://www.clientcide.com/industry-news/msft-fixes-memory-leaks-in-ie6/</link>
		<comments>http://www.clientcide.com/industry-news/msft-fixes-memory-leaks-in-ie6/#comments</comments>
		<pubDate>Fri, 22 Jun 2007 16:15:29 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA['Industry' News]]></category>
		<category><![CDATA[Browser Bugs]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/industry-news/msft-fixes-memory-leaks-in-ie6/</guid>
		<description><![CDATA[Hell must have frozen over or something. I don&#8217;t know if this just fixes certain kinds of leaks or all of them; explicit circular references in your code should still be avoided. Xopus, via Snook:
At Xopus we develop a pretty big (~50k lines) JavaScript application to edit XML documents through a WYSIWYG interface. With such [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/industry-news/msft-fixes-memory-leaks-in-ie6/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IE and &#8220;Operation Aborted&#8221;</title>
		<link>http://www.clientcide.com/code-snippets/manipulating-the-dom/ie-and-operation-aborted/</link>
		<comments>http://www.clientcide.com/code-snippets/manipulating-the-dom/ie-and-operation-aborted/#comments</comments>
		<pubDate>Thu, 05 Apr 2007 00:48:44 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Browser Bugs]]></category>
		<category><![CDATA[Manipulating the Dom]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/code-snippets/manipulating-the-dom/ie-and-operation-aborted/</guid>
		<description><![CDATA[Internet Explorer&#8217;s behavior sometimes really, really makes me angry.
We recently rolled out a copy of our javascript libraries after much testing and, a few hours later, discovered a page on our site that IE was barfing on. Specifically, the page would load about half way and then announce that it could not load the page [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/code-snippets/manipulating-the-dom/ie-and-operation-aborted/feed/</wfw:commentRss>
		<slash:comments>57</slash:comments>
		</item>
		<item>
		<title>Beware: object = object has a pitfall</title>
		<link>http://www.clientcide.com/best-practices/beware-object-object-has-a-pitfall/</link>
		<comments>http://www.clientcide.com/best-practices/beware-object-object-has-a-pitfall/#comments</comments>
		<pubDate>Fri, 12 Jan 2007 19:43:30 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Browser Bugs]]></category>
		<category><![CDATA[Code Snippets]]></category>
		<category><![CDATA[Examples]]></category>
		<category><![CDATA[Reference]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/best-practices/beware-object-object-has-a-pitfall/</guid>
		<description><![CDATA[So I spent an entire day discovering a quirk about javascript that I must now share. In a previous post on creating default settings for classes/objects I discussed the following technique:
var Widget = new Class({
	initialize: function(element, options){
		this.element = element;
		this.options = Object.extend({
			offsetX: 0,
			offsetY: 0
		}, options &#124;&#124; {});
		this.setPosition();
	},
	setPosition: function(){
		this.element.setStyles({
			left: this.options.offsetX + &#039;px&#039;,
			top: this.options.offsetY + &#039;px&#039;
		});
	}
});
Now, this isn&#8217;t [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/best-practices/beware-object-object-has-a-pitfall/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>No more IE background flicker</title>
		<link>http://www.clientcide.com/code-snippets/visual-effects/no-more-ie-background-flicker/</link>
		<comments>http://www.clientcide.com/code-snippets/visual-effects/no-more-ie-background-flicker/#comments</comments>
		<pubDate>Tue, 26 Sep 2006 19:15:43 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Browser Bugs]]></category>
		<category><![CDATA[Visual Effects]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=167</guid>
		<description><![CDATA[Fantastic! Via ajaxian (of course):
Have you been bugged by IE background flicker?
Cristi Balan talked about the issue and the solution:
html {
  filter: expression(document.execCommand("BackgroundImageCache", false, true));
}
Cristi links to a blog posting by Dan Popa, who discovered the IE6 background image flicker fix. And while you&#8217;re on Dan&#8217;s site, check out a forensic analysis of the [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/code-snippets/visual-effects/no-more-ie-background-flicker/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IE7 css changes</title>
		<link>http://www.clientcide.com/browser-bugs/ie7-css-changes/</link>
		<comments>http://www.clientcide.com/browser-bugs/ie7-css-changes/#comments</comments>
		<pubDate>Thu, 24 Aug 2006 19:17:21 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Browser Bugs]]></category>
		<category><![CDATA[CSS]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=142</guid>
		<description><![CDATA[Brandon S. writes: The first release candidate of IE version 7 came out today&#8230;
And then on ajaxian:
The IE Team has posted more details on the IE7 CSS changes so we can all get prepared:
We are currently locking down IE7 for shipping and I wanted to give an update on the CSS work that went into [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/browser-bugs/ie7-css-changes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Aha! Memory leak fixed; a summary</title>
		<link>http://www.clientcide.com/best-practices/optimization/aha-memory-leak-fixed-a-summary/</link>
		<comments>http://www.clientcide.com/best-practices/optimization/aha-memory-leak-fixed-a-summary/#comments</comments>
		<pubDate>Mon, 26 Jun 2006 21:16:07 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Browser Bugs]]></category>
		<category><![CDATA[Examples]]></category>
		<category><![CDATA[Optimization]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=114</guid>
		<description><![CDATA[Ok. So in my previous posts I talked a lot about various ways to detect javascript leaks, what often causes them, etc. I have to libraries that are leaking, both of which use Objects that are instantiated and reference, in one form or another, elements in the DOM.
I&#8217;ve fixed my memory leaks in my popup [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/best-practices/optimization/aha-memory-leak-fixed-a-summary/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Memory leaks and Moo.fx</title>
		<link>http://www.clientcide.com/best-practices/memory-leaks-and-moofx/</link>
		<comments>http://www.clientcide.com/best-practices/memory-leaks-and-moofx/#comments</comments>
		<pubDate>Mon, 26 Jun 2006 19:00:12 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Browser Bugs]]></category>
		<category><![CDATA[Optimization]]></category>
		<category><![CDATA[moo.fx]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=113</guid>
		<description><![CDATA[Continuing in my efforts to make my code stop leaking (fun!), I&#8217;ve been working on a popup handler I wrote recently (which I plan to post and share as soon as, you know, it doesn&#8217;t leak). 
This popup handler accepts as it&#8217;s parameters (among other things) a group of items (links for example) that it [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/best-practices/memory-leaks-and-moofx/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/screencast-on-diagnosing-memory-leaks-in-ie-2/</link>
		<comments>http://www.clientcide.com/best-practices/screencast-on-diagnosing-memory-leaks-in-ie-2/#comments</comments>
		<pubDate>Fri, 23 Jun 2006 19:04:11 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Browser Bugs]]></category>
		<category><![CDATA[Examples]]></category>
		<category><![CDATA[Optimization]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=112</guid>
		<description><![CDATA[via Ajaxian: this is a somewhat old post, but this short (3min) screencast was useful in my on-going memory leak quest. Just watching it I better understand the problem and realize that previous code I&#8217;ve written will require some refactoring.
Patrick Fitzgerald posted a nice screencast explaining how he diagnosed and fixed an IE memory leak [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/best-practices/screencast-on-diagnosing-memory-leaks-in-ie-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Javascript memory leaks</title>
		<link>http://www.clientcide.com/best-practices/javascript-memory-leaks/</link>
		<comments>http://www.clientcide.com/best-practices/javascript-memory-leaks/#comments</comments>
		<pubDate>Thu, 22 Jun 2006 22:06:22 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Browser Bugs]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=111</guid>
		<description><![CDATA[It&#8217;s been a while since I last posted. Partly because I haven&#8217;t seen anything super interesting and partly because I&#8217;ve been heads-down on something super-duper secret. I&#8217;ll post on it when I&#8217;m good and ready.
The super secret thing I&#8217;m working on has a problem: it leaks. It leaks in Firefox, which I&#8217;m told is a [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/best-practices/javascript-memory-leaks/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

