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

@annevk commented on this pull request.



> + <li>Set <var>response</var>'s <a for="response">timing info</a> to the
+ result of calling <a>report timing</a> given <var>response</var>, <var>global</var>,
+ <var>initiatorType</var>, and <var>taoPass</var>.
+</ol>
+
+<p>To <dfn export>report timing with origin</dfn> given a <a for=/>response</a>
+<var>response</var>, a <a for=/>global object</a> <var>global</var>, an <a for=/>origin</a>
+<var>origin</var>, and a <a for=/>string</a> <var>initiatorType</var> (default
+"<code>other</code>"), <a>report timing</a> for <var>response</var>,
+<var>global</var>, <var>initiatorType</var>, and the result of calling <a>TAO origin check</a> with
+<var>response</var> and the result of <a lt="ASCII serialization of an origin">serializing</a>
+<var>origin</var>.
+
+<p class=note>This algorithm is used by <cite>HTML</cite> to report resource timing for
+iframes, as iframes report both to the iframe's loaded document as navigation timing and to the
+containing document as resource timing.

It seems the language comment wasn't addressed/pushed?

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

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