- From: Gérard Talbot <css21testsuite@gtalbot.org>
- Date: Mon, 3 Sep 2012 23:12:31 -0400
- To: "Arron Eicholz" <Arron.Eicholz@microsoft.com>
- Cc: "Public CSS test suite mailing list" <public-css-testsuite@w3.org>
Arron, [RC6] http://test.csswg.org/suites/css2.1/20110323/html4/absolute-replaced-height-022.htm [nightly-unstable] http://test.csswg.org/suites/css2.1/nightly-unstable/html4/absolute-replaced-height-022.htm <meta name="assert" content="An absolutely positioned inline replaced element with only one value as 'auto' solves for that value (margin-bottom)."> Firefox 15 (as reported by DOM inspector): bottom computed value: -96px margin-bottom computed value: 0px Chrome 21.0.1180.89 (as reported by Web inspector): bottom computed value: 96px margin-bottom computed value: -192px (this -192px margin-bottom is possibly what the test expected, was predicting) Opera 12.02 (as reported by DragonFly): bottom computed value: 96px margin-bottom computed value: 0px and all 3 browsers render the test identically. At least, Firefox 15 and Chrome 21 balance the constraining equation ... although any bottom + margin-bottom == -96px would balance the equation. But from the look of those data, the test is not convincing. I have no idea right now on how to improve such test. Maybe I'm missing something here.. Gérard -- Contributions to the CSS 2.1 test suite: http://www.gtalbot.org/BrowserBugsSection/css21testsuite/ CSS 2.1 Test suite RC6, March 23rd 2011: http://test.csswg.org/suites/css2.1/20110323/html4/toc.html CSS 2.1 test suite harness: http://test.csswg.org/harness/ Contributing to to CSS 2.1 test suite: http://www.gtalbot.org/BrowserBugsSection/css21testsuite/web-authors-contributions-css21-testsuite.html
Received on Tuesday, 4 September 2012 03:12:54 UTC