/resource-timing/resource-timing.html is disabled in Mozilla & Edge and flaky in WebKit

[zcorpan]

http://bocoup.github.io/wpt-disabled-tests-report/

Investigate what's up with this test:

Path	Products	Results	Bugs
/resource-timing/resource-timing.html	mozilla webkit edge	disabled [ Pass Failure ] disabled	https://bugzilla.mozilla.org/show_bug.cgi?id=1290858 https://webkit.org/b/161088 None

[zcorpan]

@toddreifsteck you wrote this test. Do you have any thoughts on how to fix it?

cc @igrigorik

[toddreifsteck]

I'll follow up with the dev who is working on some bug fixes in Resource Timing in Edge 17.

It appears that there are 2 classes of issue here:

• Universal failure: Setting 'document.domain' does not effect same-origin checks
• A number of tests use small 250 ms python server delays to ensure client Resource Timings are accurate. For some reason, the browsers seem to occasionally get these timings wrong. My guess is that we are encountering scenarios where the server delays are not long enough to ensure that another network, server or client delay isn't impacting the times. (This will take more research.)

I'll follow up with the dev that owns this and share more in a few days.

[toddreifsteck]

Follow up-- Took a minute more to debug the first issue. It appears that the document.domain test was checked in with broken code. That particular test needs a tiny bit of work to do what is intended.

I'll follow up with the dev.

[zcorpan]

@toddreifsteck ping :)