[whatwg/fetch] Pass in render blocking status via finalize and report timing (PR #1449)

<!--
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.
-->
These changes are to support addition of a render blocking status field to Perfomance resource timing. Further details are available at https://github.com/w3c/resource-timing/pull/327


- [ ] 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:
   * Chrome: …
   * Firefox: …
   * Safari: …
   * Deno (not for CORS changes): …

(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/1449


-- Commit Summary --

  * Pass in render blocking status via finalize and report timing

-- File Changes --

    M fetch.bs (8)

-- Patch Links --

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

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


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

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

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