[whatwg/fetch] Specify connection timing for HTTP/3 (PR #1417)

- `secure connection start` is identical to `connection start`
  (TLS and connecting are part of the same flow in HTTP/3)

- `connection end` is right after the handshake

This corresponds to current Chromium implementation.

Closes https://github.com/w3c/navigation-timing/issues/165


<!--
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:
   * Currently WPT doesn't have support for H3 (except for `WebTransport`, TBD)
- [ ] [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/1417


-- Commit Summary --

  * Specify connection timing for HTTP/3

-- File Changes --

    M fetch.bs (9)

-- Patch Links --

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

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


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

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

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