Comments on: An IE7 CSS test suite http://www.webdevout.net/tidings/2006/08/20/an-ie7-css-test-suite/ Updates on the march of progress. A weblog about web design, standards, web browsers, and the overall health of the Web. Fri, 21 Nov 2008 20:22:42 +0000 http://wordpress.org/?v=2.0.1 by: David Hammond http://www.webdevout.net/tidings/2006/08/20/an-ie7-css-test-suite/#comment-1147 Mon, 21 Aug 2006 03:04:41 +0000 http://www.webdevout.net/tidings/2006/08/20/an-ie7-css-test-suite/#comment-1147 Most of the issues are incorrect implementations of CSS 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't count features that rely on missing features. For instance, the missing support for <code>:before</code> is indicated, but I don't bother to test counters and positioning of generated content because at this stage it would be redundant. Most of the issues are incorrect implementations of CSS features, but some are features that are missing altogether, such as outline and :before. I only point out such issues once per feature, and I don’t count features that rely on missing features. For instance, the missing support for :before is indicated, but I don’t bother to test counters and positioning of generated content because at this stage it would be redundant.

Posted using (Not Specified) .

]]> by: Jeff Fohl http://www.webdevout.net/tidings/2006/08/20/an-ie7-css-test-suite/#comment-1146 Mon, 21 Aug 2006 02:58:01 +0000 http://www.webdevout.net/tidings/2006/08/20/an-ie7-css-test-suite/#comment-1146 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't - doesn'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? 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’t - doesn’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?

Posted using (Not Specified) .

]]>