1618543 - [rel=preload] Let `fetch()` use "fetch" preloads

Status: RESOLVED FIXED

(Core :: DOM: Networking, enhancement, P1)

Description

[Honza Bambas (:mayhemer)]

Part of Design documentation for rel=preload

There are two main points to fulfill:

1. At the place fetch opens its HTTP channel, look for an existing preload in Document.PreloadService using the key as defined in the design doc above. The "as" part of the key shall be "fetch". The exact content for the attributes part of the key is yet to be determined for fetch. If a prelaod is found in the PreloadService, then instead of opening a new channel, use the AsyncConsume method of the preload to get the data. If not, or if AsyncConsume fails, open a new HTTP channel as we do now.
2. FetchDriver has to implement PreloaderBase and after it opens its HTTP channel, register itself in Document.PreloadService so that later added <link preload> tags get the onload/onerror notifications and don't open a second channel.
   This goes against the finding on how Chrome behaves. A used fetch preload is removed from the preload hash table, following preloads create a new network request.

Comment 1

[Honza Bambas (:mayhemer)]

Attachment: Bug 1618543 - Let `fetch()` use "fetch" preloads, r=ckerschb

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/4068b1f7a903
Let `fetch()` use "fetch" preloads, r=baku

Comment 3

[Narcis Beleuzu [:NarcisB]]

https://hg.mozilla.org/mozilla-central/rev/4068b1f7a903