W3C home > Mailing lists > Public > public-css-testsuite@w3.org > May 2012

[RC6] border-bottom-width-applies-to-008 and 014 have issues

From: Gérard Talbot <css21testsuite@gtalbot.org>
Date: Wed, 23 May 2012 22:34:45 -0400
Message-ID: <25ebc9266ceacaf035fc8785562ff0d6.squirrel@ed-sh-cp3.entirelydigital.com>
To: "Arron Eicholz" <Arron.Eicholz@microsoft.com>
Cc: "Public CSS test suite mailing list" <public-css-testsuite@w3.org>



The 4 non-breakable-spaces will use different width and different height
depending on default font as set by the user.

With DejaVu Serif, the width is 124px for Firefox 12, Opera 11.64 and
Chrome 19.0.1084.52 and the height is 209px for Firefox 12 and Opera
11.64 and 208px for Chrome 19.0.1084.52.

With FreeSerif, the width is 96px for Firefox 12, Opera 11.64 and Chrome
19.0.1084.52 and the height is 212px for Firefox 12 and Opera 11.64 and
220px for Chrome 19.0.1084.52.

Since creating a reftest implies to use another method, feature, then
I'm afraid this test can not be reftested. I think the test should be
reworked. There must be a way to overcome this issue; Ahem font is an




Firefox 12 and Opera 11.64 display the border-bottom black square at an
offsetTop of 66px, therefore giving, allocating 15px so that the
'inline-table' can be baseline-aligned. Chrome 19.0.1084.52 displays the
border-bottom black square at an offsetTop of 51px suggesting that it
does not baseline-align the inline-table.

Bug 23544: The baseline of an 'inline-table' is the baseline of the
first row of the table

Chrome 19.0.1084.52 fails

This 15px vertical gap is not predictable as it also depends on the font
in use. It can change and it does change when using, say, FreeSerif and
DejaVu Serif fonts.

So, as coded, it is not possible to reftest this test. Also, this test
as coded and as worded, can result in a false positive because vertical
alignment of the black square has not been taken into
account/consideration. Although baseline-alignment of an inline-table
may not have been the purpose/goal of that test, it does affect the
ability to create a reftest.

Contributions to the CSS 2.1 test suite:

CSS 2.1 Test suite RC6, March 23rd 2011:

CSS 2.1 test suite harness:

Contributing to to CSS 2.1 test suite:
Received on Thursday, 24 May 2012 02:35:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 20 January 2023 19:58:18 UTC