- From: Geoffrey Sneddon <me@gsnedders.com>
- Date: Fri, 6 Nov 2015 13:50:30 +0000
- To: "Zhang, Zhiqiang" <zhiqiang.zhang@intel.com>, "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>
On 06/11/15 13:39, Zhang, Zhiqiang wrote: > Hi, > >> From: Geoffrey Sneddon [mailto:me@gsnedders.com] >> Sent: Friday, November 6, 2015 9:12 PM >> To: public-css-testsuite@w3.org >> Subject: Requirement to remove fonts after test >> >> Hello again, >> >> A number of tests contain: >> >>> Post Test: Remove test font after running the test. >> >> It's not clear to me why any of them actually require the test font to be >> removed after the test. Anyone have any idea why it's there? > > I haven't checked the tests. Generally a test case needs to do cleanup before exit, say post-condition (here is the font), so that it has no impact on the rest tests. I'm not denying it's a good idea in principle—just most people's CI systems aren't designed such that they can just install a font for *one* test! I have now found some fallout from it: css21/fonts/font-family-rule-006.xht Prima-facie, it makes sense to have such a test distinct from the others. One can imagine an implementation for font-family: "sans-serif": 1. If there is a font family matching the name "sans-serif", use that. 2. If "sans-serif" is a generic name, use the generic font. 3. Fallback to next item in font-family list, goto 1. Therefore, I guess it's reasonable to test both with a font that matches "sans-serif" and without any font matching it… /Geoffrey.
Received on Friday, 6 November 2015 13:51:00 UTC