- From: Geoffrey Sneddon <gsneddon@opera.com>
- Date: Tue, 06 Aug 2013 10:55:22 +0100
- To: Tobie Langel <tobie@w3.org>
- CC: Peter Linss <peter.linss@hp.com>, Rebecca Hauck <rhauck@adobe.com>, James Graham <james@hoppipolla.co.uk>, "public-test-infra@w3.org" <public-test-infra@w3.org>
On 05/08/13 18:02, Tobie Langel wrote: >> I'm also working on making the build system more generic so it can run against the new repo layout. This has to be completed before we can do any significant rearranging of our files. > Could you share the requirements of the build tools somewhere? The rest of the main repo doesn't need a build step, the files just need to be (properly) served. We need to discuss a plan to be able to do something similar with the CSS WG content as we can't require a build step for just parts of the repo (we could however, serve the files in such a way that they appear to have been built). The big thing about the CSS testsuite build system is the assumption that one doesn't know what it's being run on. It assumes that there are implementations that only support HTML (e.g., WeasyPrint, IE<9) and those that only support XML (PrinceXML until some relatively recent release). As such, all the tests are written in XHTML (except for a few HTML only ones), and then programmatically converted into HTML. I think, elsewhere, we've simply assumed everyone supports both HTML and XHTML. Ultimately, therefore, it would appear to depend on the importance of running in UAs that do not support both. -- Geoffrey Sneddon — Opera Software <http://gsnedders.com> <http://opera.com>
Received on Tuesday, 6 August 2013 09:56:19 UTC