1905759 - ResourceTiming and NavigationTiming nextHopProtocol should be empty for cached resources

Status: UNCONFIRMED

(Core :: DOM: Performance, defect)

Description

[Nic Jansma]

Steps to reproduce:

1. Navigate to https://dev.nicj.net/nexthopprotocol-transfersize.html
2. This repro page reports the nextHopProtocol and transferSize of the page (NavigationTiming) and a simple Fetch (ResourceTiming)
3. On the initial page load, you should see h2 and some amount of bytes transferred
4. If you click on "navigate to same page on domain 1" it'll re-navigate to the same page, which should be in the HTTP cache
5. The nextHopProtocol is still listed as h2 even though transferSize=0 (it's loaded from the disk or memory cache)

Actual results:

The nextHopProtocol is still listed as h2 even though transferSize=0 (it's loaded from the disk or memory cache)

Expected results:

ResourceTiming specifies that content fetched from application caches should have nextHopProtocol be empty:

https://w3c.github.io/resource-timing/#sec-performanceresourcetiming

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:fdoty, could you have a look please?

For more information, please visit BugBot documentation.