<?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>Jumping Through Hoops &#187; Microsoft</title>
	<atom:link href="http://blog.jameshiggs.com/tags/microsoft/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jameshiggs.com</link>
	<description>James Higgs&#039;s Blog</description>
	<lastBuildDate>Sun, 04 Sep 2011 12:46:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Microsoft screw the pooch again</title>
		<link>http://blog.jameshiggs.com/2008/03/04/microsoft-screw-the-pooch-again/</link>
		<comments>http://blog.jameshiggs.com/2008/03/04/microsoft-screw-the-pooch-again/#comments</comments>
		<pubDate>Tue, 04 Mar 2008 09:51:49 +0000</pubDate>
		<dc:creator>higgis</dc:creator>
				<category><![CDATA[Opinion]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[IE]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[Standards]]></category>

		<guid isPermaLink="false">http://blog.jameshiggs.com/2008/03/04/microsoft-screw-the-pooch-again/</guid>
		<description><![CDATA[Oh dear. It looked for a while as though Microsoft was going to make the right decision on compatibility vs. standards compliance in IE8. But they&#8217;ve reversed their decision now. Why? The Microsoft Interoperability Principles. I pointed out the reasons that their original approach was the right one a few weeks ago. So, once again, [...]]]></description>
			<content:encoded><![CDATA[<p>Oh dear. It looked for a while as though Microsoft was going to make the right decision on compatibility vs. standards compliance in IE8. <a href="http://blogs.msdn.com/ie/archive/2008/03/03/microsoft-s-interoperability-principles-and-ie8.aspx">But they&#8217;ve reversed their decision now</a>. Why? The <a href="http://www.microsoft.com/presspass/presskits/interoperability/default.mspx">Microsoft Interoperability Principles</a>.</p>
<p><a href="http://blog.jameshiggs.com/2008/01/22/microsoft-finally-gets-the-message-on-browser-compatibility/">I pointed out the reasons that their original approach was the right one a few weeks ago</a>.</p>
<p>So, once again, a press release trumps common sense. Idiots.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.jameshiggs.com/2008/03/04/microsoft-screw-the-pooch-again/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Microsoft finally gets the message on browser compatibility</title>
		<link>http://blog.jameshiggs.com/2008/01/22/microsoft-finally-gets-the-message-on-browser-compatibility/</link>
		<comments>http://blog.jameshiggs.com/2008/01/22/microsoft-finally-gets-the-message-on-browser-compatibility/#comments</comments>
		<pubDate>Tue, 22 Jan 2008 14:38:14 +0000</pubDate>
		<dc:creator>higgis</dc:creator>
				<category><![CDATA[Opinion]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[Browsers]]></category>
		<category><![CDATA[IE]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[Standards]]></category>

		<guid isPermaLink="false">http://blog.jameshiggs.com/2008/01/22/microsoft-finally-gets-the-message-on-browser-compatibility/</guid>
		<description><![CDATA[When Microsoft released Internet Explorer 7 they broke a huge number of sites. Why? They had tried to make IE7 standards-compatible, but had failed to understand how much work developers had had to go through to make their sites work in IE6 in the first place. There was a load of &#8216;best practice guidance&#8217; guff [...]]]></description>
			<content:encoded><![CDATA[<p>When Microsoft released Internet Explorer 7 they broke a huge number of sites. Why? They had tried to make IE7 standards-compatible, but had failed to understand how much work developers had had to go through to make their sites work in IE6 in the first place. There was a load of &#8216;best practice guidance&#8217; guff around how to make your site work in IE7, but the upshot was what I called at the time &#8216;the browser tax&#8217;.</p>
<p>Finally, finally, finally, they seem to have understood the plight of the ordinary web developer. <a href="http://blogs.msdn.com/ie/archive/2008/01/21/compatibility-and-ie8.aspx">IE8 will work as IE7 unless <em>explicitly</em> told to behave with maximum standards compatibility</a>.</p>
<p>This is what every web developer who understood the issues wanted them to do first time around. Chris Wilson describes it as a &#8216;painful and unexpected lesson&#8217;. Only because they weren&#8217;t listening properly.</p>
<p>In essence, Microsoft made this mess and they should let people decide when they&#8217;re ready to help them clean it up. It looks like that&#8217;s now going to be allowed to happen. About freaking time.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.jameshiggs.com/2008/01/22/microsoft-finally-gets-the-message-on-browser-compatibility/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

