- From: Arron Eicholz <Arron.Eicholz@microsoft.com>
- Date: Wed, 21 Jul 2010 02:38:51 +0000
- To: "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>
- Message-ID: <DD511CF6D0DA5A428D4E7C6F459BD7AB134C283F@TK5EX14MBXC138.redmond.corp.microsoft.>
I am listing the currently invalid test cases as I have found them in my review. These cases can probably be easily updated but I wanted to get a list out there so we had something to go through and try and fix. http://test.csswg.org/suites/css2.1/20100701/html4/active-selector-000.htm CSS does not define what elements can be in the :active state. Since the test has a *:active selector this causes an issue and this case is currently invalid. http://test.csswg.org/suites/css2.1/20100701/html4/active-selector-004.htm CSS does not define what elements can be in the :active state. Since the test has a *:active selector this causes an issue and this case is currently invalid. http://test.csswg.org/suites/css2.1/20100701/html4/at-charset-071.htm http://test.csswg.org/suites/css2.1/20100701/html4/character-encoding-031.htm é is missing from the p element. I have a feeling something in the build process converted it to é and added that before the p tag. http://test.csswg.org/suites/css2.1/20100701/html4/attribute-value-selector-010.htm http://test.csswg.org/suites/css2.1/20100701/html4/lang-pseudoclass-001.htm The build process seems to be stripping out the xml: namespace in elements when build as HTML. This shouldn't happen in this case since the test is testing the presence of the namespace. http://test.csswg.org/suites/css2.1/20100701/html4/background-attachment-006.htm The swatch-teal.png is missing http://test.csswg.org/suites/css2.1/20100701/html4/before-after-display-types-001.htm flexbox is used in this test case along with -moz- prefixes. http://test.csswg.org/suites/css2.1/20100701/html4/before-after-dynamic-attr-001.htm double colon before and after is only valid in CSS3 http://test.csswg.org/suites/css2.1/20100701/html4/c5504-mrgn-l-002.htm Negative margin doesn't seem to define weather it should create scrolling on the viewport. http://test.csswg.org/suites/css2.1/20100701/html4/c61-phys-len-000.htm This requires screens to be properly calibrated to a specific size. Also not all credit cards are the same size. http://test.csswg.org/suites/css2.1/20100701/html4/cursor-023.htm Text is incorrect for the behavior that is specified. Plus the CSS spec does not say what image types are supported for cursors. This case cannot require a png as a valid cursor type since it is not specified what user agents are required to support for cursor images. http://test.csswg.org/suites/css2.1/20100701/html4/cursor-024.htm The CSS spec does not say what image types are supported for cursors. This case cannot require a gif as a valid cursor type since it is not specified what user agents are required to support for cursor images. http://test.csswg.org/suites/css2.1/20100701/html4/first-letter-characters-001.htm Build parse error. http://test.csswg.org/suites/css2.1/20100701/html4/first-line-floats-002.htm Double colon CSS3 definition for first-line is not valid for CSS 2.1. http://test.csswg.org/suites/css2.1/20100701/html4/first-line-pseudo-006.htm Spec is unclear if an empty block is ignored for first-line. http://test.csswg.org/suites/css2.1/20100701/html4/floats-107.htm Painting of the positioned element comes after the painting of the floats thus the red should be visible. This case needs a good rewrite. http://test.csswg.org/suites/css2.1/20100701/html4/floats-148.htm This test is testing an undefined assumption. I think we can still keep the case. I just think it needs better "pass" conditions. Something line "Test passes if there is a green box below or there is no box visible." http://test.csswg.org/suites/css2.1/20100701/html4/font-004.htm http://test.csswg.org/suites/css2.1/20100701/html4/font-020.htm My bugs I will fix these http://test.csswg.org/suites/css2.1/20100701/html4/font-family-name-008.htm Test assumes that the spaces would collapse and the font would match. Right now all browsers are falling back and the Fallback font will spell FAIL. http://test.csswg.org/suites/css2.1/20100701/html4/inline-replaced-width-012.htm http://test.csswg.org/suites/css2.1/20100701/html4/inline-replaced-width-013.htm swatch-green.png is only 15px high. I think we just need to fix the swatch image to be 100px tall. http://test.csswg.org/suites/css2.1/20100701/html4/inline-replaced-width-015.htm I have an update already for this issue. http://test.csswg.org/suites/css2.1/20100701/html4/inlines-008.htm The table has no height so the green is not visible http://test.csswg.org/suites/css2.1/20100701/html4/inlines-011.htm http://test.csswg.org/suites/css2.1/20100701/html4/inlines-012.htm Pass conditions do not match image shown http://test.csswg.org/suites/css2.1/20100701/html4/inlines-018.htm http://test.csswg.org/suites/css2.1/20100701/html4/inlines-019.htm class pass element is properly placed 1em down from top of viewport. Which will never overlap the FAIL text. http://test.csswg.org/suites/css2.1/20100701/html4/list-style-position-023.htm http://test.csswg.org/suites/css2.1/20100701/html4/list-style-position-024.htm The spec is loosely defined here. I think IE and Firefox have the correct rendering for the case (the upper part). Note that the bottom part of the case is supposed to be the reference. http://test.csswg.org/suites/css2.1/20100701/html4/margin-collapse-107.htm http://test.csswg.org/suites/css2.1/20100701/html4/margin-collapse-108.htm http://test.csswg.org/suites/css2.1/20100701/html4/margin-collapse-109.htm Sub-pixel rendering prevents these cases from working now. They should be changed to not have sub-pixel issues. http://test.csswg.org/suites/css2.1/20100701/html4/margin-collapse-114.htm The more I look at this the more I think the case is correct but it seems like everyone has agreed on a different behavior. Not sure what we want to do here. http://test.csswg.org/suites/css2.1/20100701/html4/margin-collapse-136.htm This cases seems to assume that an empty line box will still have height. If it has 0 height as I assume it would then the case is incorrect. http://test.csswg.org/suites/css2.1/20100701/html4/overflow-applies-to-014.htm http://test.csswg.org/suites/css2.1/20100701/html4/overflow-applies-to-015.htm Spec is not clear on behavior. What should be the proper rendering? http://test.csswg.org/suites/css2.1/20100701/html4/replaced-intrinsic-001.htm http://test.csswg.org/suites/css2.1/20100701/html4/replaced-intrinsic-002.htm http://test.csswg.org/suites/css2.1/20100701/html4/replaced-intrinsic-003.htm It seems as if the server is not properly serving the mime type for SVG in these cases. Per the HTML spec the defined type on an object tag is just a suggestion and does not override the HTTP content type. http://test.csswg.org/suites/css2.1/20100701/html4/root-box-002.htm CSS 2.1 does not define the painting order of table-caption http://test.csswg.org/suites/css2.1/20100701/html4/run-in-fixedpos-between-001.htm class defined on element is "fixed" but style block has "fixedpos". Naming issue. http://test.csswg.org/suites/css2.1/20100701/html4/table-caption-002.htm Multiple caption handling is not clearly defined in CSS. http://test.csswg.org/suites/css2.1/20100701/html4/text-decoration-088.htm The block box with text-align: right should have an underline though the pass conditions say otherwise. http://test.csswg.org/suites/css2.1/20100701/html4/units-002.htm I have an update already for this issue. http://test.csswg.org/suites/css2.1/20100701/html4/units-007.htm I'm not really even sure what this is supposed to be or how it is easily supposed to be tested. I think we can remove this test since it duplicates all other units and values tests. http://test.csswg.org/suites/css2.1/20100701/html4/white-space-control-characters-001.htm I am still working on a solution for this case. http://test.csswg.org/suites/css2.1/20100701/html4/white-space-normal-007.htm I have an update already for this issue. http://test.csswg.org/suites/css2.1/20100701/html4/z-index-020.htm test uses CSS3 outline-offset. And Outlines can be drawn at 2 different stacking contexts so outline in this tests is flaky and can cause false failures. -- Thanks, Arron Eicholz
Received on Wednesday, 21 July 2010 02:39:28 UTC