Re: [whatwg/fetch] Allow timing reporting with origin (for iframes) (PR #1388)

Actually there's something missing here I believe... the iframe and the embedder might have a different cross-origin isolated capability, so the timing might need to be coarsened if the embedder is more strict than the frame. The same will be needed for early hints, as the timestamps are marked before the document is created.

I wonder if entries should be coarsened again when accessed (inside the `Resource Timing` spec) - which is what implementations do - it makes sure that the global object for coarsening is the one relevant to the entry regardless of how it was created.



-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1388#issuecomment-1058964033
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1388/c1058964033@github.com>