Re: [resource-timing-tests] Add TAO tests for Resource Timing (#5117)

@toddreifsteck 

the [webhook](https://w3c-test.org/submissions/5117/) of this PR was broken yesterday but @deniak fixed it today, so these test can now be run directly on the preview (see the links below):

- [`TAO = "origin, *"`](http://w3c-test.org/submissions/5117/resource-timing/resource_TAO_multi.htm), expect TAO algorithm to pass, test passes on Edge, fails on Chrome and Firefox;
- [`TAO = "null"`](http://w3c-test.org/submissions/5117/resource-timing/resource_TAO_null.htm), expect TAO algorithm to fail, test passes on Chrome and Firefox, fails on Edge;
- [`TAO = "origin"`](http://w3c-test.org/submissions/5117/resource-timing/resource_TAO_origin.htm), expect TAO algorithm to pass, test passes on Edge, fails on Firefox and Chrome;
- [`TAO = [uppercase of "origin"]`](http://w3c-test.org/submissions/5117/resource-timing/resource_TAO_origin_uppercase.htm), expect TAO algorithm to fail, test passes on Chrome and Firefox, fails on Edge;
- [`no TAO header`](http://w3c-test.org/submissions/5117/resource-timing/resource_TAO_zero.htm), expect TAO algorithm to fail, test passes on Chrome and Firefox, fails on Edge;
- [`TAO = "origin *"`](http://w3c-test.org/submissions/5117/resource-timing/resource_TAO_space.htm), expect TAO algorithm to fail, test passes on Firefox and Chrome, fails on Edge;

(here `origin` means "a case-sensitive match for the value of the origin", using EdgeHTML 15.15063, Firefox 55, Chrome 59)

Do these test cases make sense to you?



View on GitHub: https://github.com/w3c/web-platform-tests/pull/5117#issuecomment-293934412

Received on Thursday, 13 April 2017 15:46:53 UTC