From a triage[1] of currently failing WPT resource-timing tests[2], the following WebKit test failures may (or may not be) be related to Timing-Allow-Origin (TAO) validations: https://wpt.fyi/results/resource-timing/TAO-case-insensitive-null-opaque-origin.sub.html?label=master&label=experimental&aligned https://wpt.fyi/results/resource-timing/TAO-crossorigin-port.sub.html?label=master&label=experimental&aligned https://wpt.fyi/results/resource-timing/resource_TAO_multi_wildcard.html?label=master&label=experimental&aligned https://wpt.fyi/results/resource-timing/resource_TAO_match_wildcard.htm?label=master&label=experimental&aligned https://wpt.fyi/results/resource-timing/resource-reload-TAO.sub.html?label=master&label=experimental&aligned https://wpt.fyi/results/resource-timing/nextHopProtocol-tao-protected.https.html?label=master&label=experimental&aligned https://wpt.fyi/results/resource-timing/crossorigin-sandwich-TAO.sub.html?label=master&label=experimental&aligned [1] https://github.com/w3c/resource-timing/issues/233 [2] https://wpt.fyi/results/resource-timing?label=master&label=experimental&aligned
<rdar://problem/69368901>