1. Visit https://jaffathecake.runkit.io/5915ff685662e900117e6e32/branches/master/ to install the service worker.
2. Refresh the page to confirm navigation preload is enabled. It should respond "Received preload request".
3. Enable "Preserve log" in devtools
4. Navigate to https://jaffathecake.runkit.io/5915ff685662e900117e6e32/branches/master/slow/.

Code for the test: https://runkit.com/jaffathecake/5915ff685662e900117e6e32.

I see "Preload response rejected!" in the log. It seems like Chrome is aborting the preloadResponse because I don't use it in the response, but the spec doesn't say this should happen.

Practically, developers may want to respond from the cache, but use the preloadResponse to populate the cache for next time, in a kind-of stale-while-revalidate model, but Chrome's current behaviour prevents this.

I think it's good that Chrome aborts responses that aren't needed, but this should be done when event.preloadResponse is GC'd, so the abort isn't observable by JS.