[whatwg/fetch] Don't automaticallly report resource timing for cross-origin TAO-fail… (PR #1579)

… iframes

Reporting the response end time for an iframe may leak information about user interaction with that iframe.

See w3c/resource-timing#340

<!--
Thank you for contributing to the Fetch Standard! Please describe the change you are making and complete the checklist below if your change is not editorial.
-->

- [ ] At least two implementers are interested (and none opposed):
   * …
   * …
- [ ] [Tests](https://github.com/web-platform-tests/wpt) are written and can be reviewed and commented upon at:
   * …
- [ ] [Implementation bugs](https://github.com/whatwg/meta/blob/main/MAINTAINERS.md#handling-pull-requests) are filed:
   * Chromium: …
   * Gecko: …
   * WebKit: …
   * Deno (not for CORS changes): …
- [ ] [MDN issue](https://github.com/whatwg/meta/blob/main/MAINTAINERS.md#handling-pull-requests) is filed: …

(See [WHATWG Working Mode: Changes](https://whatwg.org/working-mode#changes) for more details.)

You can view, comment on, or merge this pull request online at:

  https://github.com/whatwg/fetch/pull/1579


-- Commit Summary --

  * Don't automaticallly report resource timing for cross-origin TAO-fail iframes

-- File Changes --

    M fetch.bs (24)

-- Patch Links --

https://github.com/whatwg/fetch/pull/1579.patch

https://github.com/whatwg/fetch/pull/1579.diff


-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1579

You are receiving this because you are subscribed to this thread.

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