<?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: An IE7 CSS test suite</title>
	<atom:link href="http://www.webdevout.net/tidings/2006/08/20/an-ie7-css-test-suite/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webdevout.net/tidings/2006/08/20/an-ie7-css-test-suite/</link>
	<description>Updates on the march of progress. A weblog about web design, standards, web browsers, and the overall health of the Web.</description>
	<lastBuildDate>Wed, 14 Dec 2011 14:45:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: David Hammond</title>
		<link>http://www.webdevout.net/tidings/2006/08/20/an-ie7-css-test-suite/comment-page-1/#comment-1147</link>
		<dc:creator>David Hammond</dc:creator>
		<pubDate>Mon, 21 Aug 2006 03:04:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.webdevout.net/tidings/2006/08/20/an-ie7-css-test-suite/#comment-1147</guid>
		<description>Most of the issues are incorrect implementations of CSS features, but some are features that are missing altogether, such as &lt;code&gt;outline&lt;/code&gt; and &lt;code&gt;:before&lt;/code&gt;. I only point out such issues once per feature, and I don&#039;t count features that rely on missing features. For instance, the missing support for &lt;code&gt;:before&lt;/code&gt; is indicated, but I don&#039;t bother to test counters and positioning of generated content because at this stage it would be redundant.</description>
		<content:encoded><![CDATA[<p>Most of the issues are incorrect implementations of <abbr title="Cascading Style Sheets">CSS</abbr> features, but some are features that are missing altogether, such as <code>outline</code> and <code>:before</code>. I only point out such issues once per feature, and I don&#8217;t count features that rely on missing features. For instance, the missing support for <code>:before</code> is indicated, but I don&#8217;t bother to test counters and positioning of generated content because at this stage it would be redundant.</p>
<p class="postdetails"><em>Posted using Mozilla Firefox 1.5.0.6 on Linux.</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Fohl</title>
		<link>http://www.webdevout.net/tidings/2006/08/20/an-ie7-css-test-suite/comment-page-1/#comment-1146</link>
		<dc:creator>Jeff Fohl</dc:creator>
		<pubDate>Mon, 21 Aug 2006 02:58:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.webdevout.net/tidings/2006/08/20/an-ie7-css-test-suite/#comment-1146</guid>
		<description>David -

This is very interesting. I really like this approach in that it gives a quick visual indicator of whether something is working properly or not. The Acid2 test, which is sort of a binary test - either it works or it doesn&#039;t - doesn&#039;t provide a lot of information in the output of the test as to what is exactly working and what is not. Of course, you are focusing specifically on things that you consider to be bugs in IE7 only - so perhaps I am comparing apples to oranges here.

This test seems to suggest that you see 30 bugs currently in the rendering engine of IE7b3. How do you define a bug? Does a CSS specification that is not supported count as a bug, or only incorrect implemenations of specifications?</description>
		<content:encoded><![CDATA[<p>David -</p>
<p>This is very interesting. I really like this approach in that it gives a quick visual indicator of whether something is working properly or not. The Acid2 test, which is sort of a binary test &#8211; either it works or it doesn&#8217;t &#8211; doesn&#8217;t provide a lot of information in the output of the test as to what is exactly working and what is not. Of course, you are focusing specifically on things that you consider to be bugs in IE7 only &#8211; so perhaps I am comparing apples to oranges here.</p>
<p>This test seems to suggest that you see 30 bugs currently in the rendering engine of IE7b3. How do you define a bug? Does a <abbr title="Cascading Style Sheets">CSS</abbr> specification that is not supported count as a bug, or only incorrect implemenations of specifications?</p>
<p class="postdetails"><em>Posted using Mozilla Firefox 1.5.0.6 on Windows.</em></p>
]]></content:encoded>
	</item>
</channel>
</rss>
