W3C home > Mailing lists > Public > public-css-testsuite@w3.org > March 2016

[css-writing-modes] full-width-001 full-width-002 full-width-003 tests

From: Gérard Talbot <css21testsuite@gtalbot.org>
Date: Mon, 28 Mar 2016 18:13:31 -0400
To: "Elika 'fantasai' Etemad (lists)" <fantasai.lists@inkedblade.net>, Koji Ishii <kojiishi@gluesoft.co.jp>
Cc: Public CSS Test suite mailing list <public-css-testsuite@w3.org>
Message-ID: <e266beca7c77294bc21eb5d2e96fbc67@gtalbot.org>
Koji, Elika,








I believe full-width-001 full-width-002 full-width-003 tests should be 
tweaked and tuned because I believe they are not precise and they are 
not perfectly reliable, not perfectly revealing.

For example full-width-002 test:

First, that full-width-002.htm uses a very misleading class name "tcy"

.tcy {
   text-transform: full-width;

Second, the "6" (6 == &#54; or &x36; or U+0036: In basic latin range: 
ASCII Digits) versus "6" (6 == &#65302;  or &xFF16; or U+FF16: 
full-width 6 : In Halfwidth and Fullwidth Forms range  
http://unicode.org/charts/PDF/UFF00.pdf) (you have to have good eyes to 
notice the difference of glyphs): one is the full-width version of the 


Third, as coded, it looks like both <p> are tests, are being tested 
(because the wrapping div has the class name "test") but both <p> are 
not tests. The first (in source code order) <p> should be the test and 
is the test; the second (in source code order) <p> should be the 
reference and is the comparing reference. What you should have instead 
in that full-width-002.htm test is a structure like this:

   <p id="test"> ...</p>
   <p id="reference"> ...</p>

This structure would improve understandability of the test.

Fourth, as I suspected, the "6" should not be part of that 
full-width-002.htm test because it is not what's being tested, is not 
what is the goal, target of the test (as stated by the test's text 
assert). The "19" is the sole target of the test.

That full-width-002.htm test is not reliable precisely because some 
browsers (Chrome 49+) supports and implements 'text-combine-upright: 
all' while some others (Firefox 45+) supports and implements 
'text-transform: full-width'. By breaking, splitting the test into 2 
separate and distinct sub-tests, we would clearly and cleanly see which 
browsers support which properties.

Draft 'text-transform: full-width' test applied on a single ASCII digit:
Firefox 45 passes that full-width-00x.xht test while Chrome 49 and 
Chrome 51.0.2687.0 fail that full-width-00x.xht test.

Test Format Guidelines

Test Style Guidelines

Test Templates

CSS Naming Guidelines

Test Review Checklist

CSS Metadata
Received on Monday, 28 March 2016 22:14:04 UTC

This archive was generated by hypermail 2.3.1 : Monday, 28 March 2016 22:14:08 UTC