- From: Ilya Grigorik <web-platform-tests-notifications@w3.org>
- Date: Thu, 27 Apr 2017 05:36:51 GMT
- To: public-web-platform-tests-notifications@w3.org
@siusin I think some of those results are not quite right due to an unrelated (missing) `Access-Control-Allow-Origin` policy.. Although it hints that Edge may not be enforcing it? =/ E.g. for the iframe_TAO_origin test (TAO = "origin") the test is marked as failing on Chrome, but if you look at the console logs, you'l see... ``` iframe_TAO_origin.html:14 XMLHttpRequest cannot load http://www.w3c-test.org/submissions/5117/resource-timing/resources/TAOResponse.py?tao=origin&origin=http://w3c-test.org/submissions/5117. The 'Access-Control-Allow-Origin' header has a value 'http://w3c-test.org/submissions/5117' that is not equal to the supplied origin. Origin 'http://w3c-test.org' is therefore not allowed access. ``` Could you add the ACAO header and rerun the tests? --- As an aside, relevant Chrome bugs: 1. [crbug.com/651861]() -- Timing-Allow-Origin should support list (comma separated) semantics 1. [crbug.com/410875]() -- Timing-Allow-Origin should not accept a space separated list of origins View on GitHub: https://github.com/w3c/web-platform-tests/pull/5117#issuecomment-297616634
Received on Thursday, 27 April 2017 05:37:03 UTC