- From: Geoffrey Sneddon via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Mar 2018 22:44:16 +0000
- To: public-css-archive@w3.org
Notwithstanding the web-platform-tests documentation issues (see https://github.com/w3c/web-platform-tests/issues/10177), I think there's a number of CSS WG specific issues: * The test build system makes it hard to find what file(s!) you need to modify to fix a test if you're looking at http://test.csswg.org/harness/ or http://test.csswg.org/suites/ (which is a large part of https://github.com/w3c/csswg-drafts/issues/2378 AFAICT) * The report issue button on tests at http://test.csswg.org/harness/ points at Shepherd which is read-only (and there's nothing on Shepherd to make that clear). We could do with decent documentation on the build system (or, as @dbaron says, get rid of it) and how to deal with various things (like the growing list of warnings it produces when being built, and how you should know whether any warnings were caused by you, etc.). -- GitHub Notification of comment by gsnedders Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2438#issuecomment-376335762 using your GitHub account
Received on Monday, 26 March 2018 22:44:27 UTC