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 stricter 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.
> 
> @annevk WDYT?

Though from what I understand that would fail? I'm not familiar enough with the case of opening a non-strict iframe inside a strict frame, I guess it would fail anyway?

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

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