servo/tests/wpt/web-platform-tests/referrer-policy/css-integration
2019-04-03 00:53:26 -04:00
..
child-css Update web-platform-tests to revision 0a28ecf697d96db228f8382db0e41f1c54314dad 2019-04-03 00:53:26 -04:00
font-face Update web-platform-tests to revision 0a28ecf697d96db228f8382db0e41f1c54314dad 2019-04-03 00:53:26 -04:00
image Update web-platform-tests to revision 0a28ecf697d96db228f8382db0e41f1c54314dad 2019-04-03 00:53:26 -04:00
svg Update web-platform-tests to revision 8805f23ef629338b6d28ae25cc13839e99acea1b 2019-02-23 23:29:05 -05:00
css-test-helper.js Update web-platform-tests to revision 0a28ecf697d96db228f8382db0e41f1c54314dad 2019-04-03 00:53:26 -04:00
README.md Update web-platform-tests to revision 0a28ecf697d96db228f8382db0e41f1c54314dad 2019-04-03 00:53:26 -04:00

These tests exercise different ways to fetch a resource (image, font-face, svg references), generated via the sub-resource python script in ./generic/subresource/ (for example, loading an image: /common/security-features/subresource/image.py?id=<UUID>) and later verify the headers used to fetch the resource.

Since there is no way to wait for a resource referenced from CSS to be loaded, all tests use step_timeout() to delay the verification step until after the resource (hopefully) was loaded.

Since there is also no way to retrieve headers (or other information) from resources loaded via CSS, we store the headers with the given UUID as key on the server, and retrieve them later via an XHR, for example: /common/security-features/subresource/image.py?id=<UUID>&report-headers.