Resource Timing API reports times for cross-origin resources without Timing-Allow-Origin header

Fixed Issue #297416


Jun 6, 2014
This issue is public.
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce


Repro Steps:

Expected Results:

According to the spec (

In the absence of the Timing-Allow-Origin HTTP response header, these attributes must be set to zero: redirectStart, redirectEnd, domainLookupStart, domainLookupEnd, connectStart, connectEnd, requestStart, responseStart and secureConnectionStart, if supported by the user agent.

You can see that these attributes are not in fact set to 0.

Actual Results:


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Tony S.”

      Changed Assigned To from “Tony S.” to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Matt K.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Matt K.” to “IE F.”

      Changed Status from “Confirmed” to “Won’t fix”

      Changed Status from “Won’t fix” to “Fixed”

      Changed Status from “Fixed” to “Won’t fix”

      Changed Assigned To to “Israel H.”

      Changed Status from “Won’t fix”

      Changed Assigned To from “Israel H.” to “Rob T.”

      Changed Assigned To from “Rob T.” to “Ali A.”

      Changed Assigned To from “Ali A.” to “Todd R.”

      Changed Status to “Fixed”

    You need to sign in to your Microsoft account to add a comment.

    Sign in