[FYI] Report Critical-CH caused restart in NavigationTiming

[arichiv]

こんにちは 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 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 so that developers can know if a restart occurred and impacted timing.

• Explainer: [url]
• GitHub repo (if you prefer feedback filed there): [url]
• Primary contacts (and their relationship to the specification):
  • Ari Chivukula, Google
• Organization/project driving the design: Chromium
• External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): https://crbug.com/1425910

[slightlyoff]

An FYI for the TAG that this feature has an I2S out and was filed late. Any quick feedback would be helpful.

[cynthia]

Discussed in breakout today, LGTM (meaning the folks in the call today).