W3C home > Mailing lists > Public > public-css-testsuite@w3.org > June 2015

Re: path to support files

From: Linss, Peter <peter.linss@hp.com>
Date: Tue, 16 Jun 2015 17:17:25 +0000
To: Florian Rivoal <florian@rivoal.net>
CC: "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>
Message-ID: <4072E151-B82A-48A9-818C-9927E2B3A909@hp.com>
This never worked (yet). The build system does fix up relative paths for reference files, but not support files. The way to handle this is to create a support directory in the same directory as the test and copy the necessary support file(s) there, then you use the relative path "support/green.ico".

Both Shepherd and the build system will recognize the duplicate support files and have only one copy in the build output.

Peter

On Jun 16, 2015, at 4:04 AM, Florian Rivoal <florian@rivoal.net> wrote:

> Hi,
> 
> I have a TC that uses an image file.
> 
> When loading the TC through the test harness, loading the image fails with a 404.
> http://test.csswg.org/harness/test/css-ui-3_dev/section/6.1.1.1/
> 
> When loading the TC through shepherd, loading the image succeeds (whether the test passes in browsers is another question, but the image is accessible at the expected path).
> 
> In the repo, the test file is "css-ui-3/canvas-cursor-001.html", and the image it uses is "support/green.ico"
> The TC refers to the image as "../support/green.ico".
> 
> Has something changed recently on test harness that causes relative url resolution to work differently, or has this never worked? If this is not supposed to work, what's the correct way of doing this?
> 
> - Florian
> 
> 
> 
> 


Received on Tuesday, 16 June 2015 17:18:59 UTC

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