[w3ctag/design-reviews] [FYI] Report Critical-CH caused restart in NavigationTiming (Issue #833)

こんにちは TAG-さん!

I wanted to give TAG a heads up about "Report Critical-CH caused restart in NavigationTiming".

Websites can indicate that a particular [Client Hint](https://wicg.github.io/client-hints-infrastructure/) is critical to the page by including it in a Critical-CH HTTP response header. Doing so will trigger a connection restart if the hint listed in the Critical-CH HTTP response header could be (but wasn’t) included in the HTTP request initially sent. We should indicate this has happened in [Navigation Timing](https://github.com/w3c/navigation-timing) so that developers can know if a restart occurred and impacted timing.

  - Explainer: [[url]](https://groups.google.com/a/chromium.org/g/blink-dev/c/f28WWMD8HVE)
  - GitHub repo (if you prefer feedback filed there): [[url]](https://github.com/w3c/navigation-timing/pull/188)
  - Primary contacts (and their relationship to the specification):
      - [Ari Chivukula](@arichiv), Google
  - Organization/project driving the design: Chromium
  - External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): https://crbug.com/1425910


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/833
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/833@github.com>