The Resource Timing(RT) API exposes the `nextHopProtocol` field to describe the underlying connection type used to fetch a resource. We're removing an old special-case where the `nextHopProtocol` of cross-origin requests were exposed more broadly than other fields in RT. This means we will more closely follow the relevant specifications and prevent leaking potentially sensitive connection information across origin boundaries.

Specification

Specification link


Specification currently under development in a Working Group

Status in Chromium

Blink>PerformanceAPIs>ResourceTiming


In development (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

Owner

Last updated on 2022-01-21