Re: [ResourceTiming] "timing allow check" steps depend on underdefined behavior

On 5/22/14, 12:15 PM, Jatinder Mann wrote:
> Good point, not all cross-origin fetches will have an Origin header. What if we simplified step 3 of the algorithm as so:
> 3.     If the value of Timing-Allow-Origin is not a match for the value of the origin of the current document

What does "current document" mean?


Received on Thursday, 22 May 2014 16:42:58 UTC