<?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: Testing websites in IE6, IE7 and IE8 on a Mac</title>
	<atom:link href="http://www.daretothink.co.uk/blog/testing-websites-in-ie6-ie7-and-ie8-on-a-mac/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.daretothink.co.uk/blog/testing-websites-in-ie6-ie7-and-ie8-on-a-mac/</link>
	<description>Specialists in Wordpress, Websites and Print</description>
	<lastBuildDate>Tue, 24 Jan 2012 09:38:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
	<item>
		<title>By: Spencer Sundell</title>
		<link>http://www.daretothink.co.uk/blog/testing-websites-in-ie6-ie7-and-ie8-on-a-mac/#comment-8</link>
		<dc:creator>Spencer Sundell</dc:creator>
		<pubDate>Tue, 14 Sep 2010 22:36:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.daretothink.co.uk/?p=1156#comment-8</guid>
		<description>It is critical to note that in reality, using IE8 in IE7 mode is *not* a 100% accurate emulation of genuine IE7.  I&#039;ve run into this problem myself on a number of occasions.  While pretty close, there are differences in how some aspects of CSS rendering and JS parsing operate.

Therefore, the best practice is to use IE8 in IE7 for rough unit testing during development, and then do a full pass using a genuine install of (real) IE7.  This can be done using a virtual machine instance, as described above for IE6.

This MSDN blog post has some further information along these lines:
http://blogs.msdn.com/b/ie/archive/2009/03/12/site-compatibility-and-ie8.aspx

Hope this helps!

Regards...</description>
		<content:encoded><![CDATA[<p>It is critical to note that in reality, using IE8 in IE7 mode is *not* a 100% accurate emulation of genuine IE7.  I&#8217;ve run into this problem myself on a number of occasions.  While pretty close, there are differences in how some aspects of CSS rendering and JS parsing operate.</p>
<p>Therefore, the best practice is to use IE8 in IE7 for rough unit testing during development, and then do a full pass using a genuine install of (real) IE7.  This can be done using a virtual machine instance, as described above for IE6.</p>
<p>This MSDN blog post has some further information along these lines:<br />
<a href="http://blogs.msdn.com/b/ie/archive/2009/03/12/site-compatibility-and-ie8.aspx" rel="nofollow">http://blogs.msdn.com/b/ie/archive/2009/03/12/site-compatibility-and-ie8.aspx</a></p>
<p>Hope this helps!</p>
<p>Regards&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced

Served from: www.daretothink.co.uk @ 2012-02-04 04:25:40 -->
