- From: Tobi Reif via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 Jan 2018 09:38:24 +0000
- To: public-css-archive@w3.org
> FWIW, this would be better discussed on the w3c/web-platform-tests repository. Thanks for the info, next I'll try to remember to submit any issues there. > the current policy is actually not to add @font-face for Ahem I'd prefer it if no test would require any specific font. But when a test writer has good reasons to require a specific font, then that font should be right there, without requiring the test-suite user to do anything regarding any required assets (fonts, images etc). @font-face is a great way to load the required font. When I supply test cases for issue reports I can't require the visitor to install the required font, so I make sure it's right there using @font-face, eg: https://bugs.chromium.org/p/chromium/issues/detail?id=800693 -> https://tobireif.com/non_site_stuff/test_case_for_font_position_report/ I ran the CSS Grid test-suite, and I inadvertently supplied potentially-incorrect test results because the tests that require a specific font don't @font-face it. The note I then saw at a later point in time is not sufficient: I already had submitted hundreds of results (running the suite in 3 browsers) before I saw the note telling me to install a font on my machine, as if we are still in a time where @font-face didn't exist 😀 You can @font-face any respective required font(s) where necessary (or eg make sure that no existing or future test requires any fonts) - or you'll probably get even more incorrect test results by people who want to contribute by running the test suite, but aren't familiar with the implicit requirements that are only obvious among test-suite contributors, WG members, etc. By the way, I'd be quite busy if every site required me to install a font, so I don't do that 😀 Supplying the font using @font-face is easy for future tests, and perhaps a script could ensure it for the existing ones. Or eg > the test harness JavaScript code [could] inject[...] @font-face for Ahem to every test[...] -- GitHub Notification of comment by tobireif Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2200#issuecomment-358914397 using your GitHub account
Received on Friday, 19 January 2018 09:38:26 UTC