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

FW: In a quick glance, all of the whitespace test file are invalid tests that don't prove anything

From: Melissa Newman <melissa@newmanfamily.org>
Date: Tue, 2 Mar 2010 11:15:29 -0500
To: <public-css-testsuite@w3.org>
Message-ID: <004301caba23$95550840$bfff18c0$@org>
I used the "X" character, because I can't type a black box on an email
message.  I thought that would have been obvious without me having to
explain myself.

I agree with you 100% that there needs to be a special font for the testing
of whitespaces that have different color squares or some type of special
character of the correct width for the different type of whitespaces.  If
that gets done, then the test files are fine.

>>There is no need to use &###; though it might be more helpful to
understand when looking at the code the actual >>character itself is just as

> Plus, how do I know if the character there is a single white space, a
> white space, a zero white space, or a control character?

>>One final question. Could you provide a couple of specific links to files
you are concerned about? I see nothing >>incorrect with the white space
testing methods at the moment but maybe we are looking at different things.

I know that the two are the same.  I was referring to when a person looks at
the code.

I am talking theoretically.  If I am just looking at the output, and not the
source code or the end results in a text editor that can display HEX, how
can anybody realistically tell the difference, with the naked eye, between a
tab, 8 single white spaces, 16 half white spaces, or 4 double white spaces?
You can't, so we are back to what you and I agree upon, that a special font
that displays the different whitespaces as different colors is needed.

Plus, we should have images that are exact measurements.  One for mm, one
for inches, etc.  So if an end result of a test is supposed to have a space
of 10mm, the tester can clearly see that the end results are 10 mm.

Melissa Newman
Received on Tuesday, 2 March 2010 16:16:05 UTC

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