ServiceWorkers' navigation preload integration
Categories
(DevTools :: Application Panel, enhancement)
Tracking
(Not tracked)
People
(Reporter: perry, Unassigned)
References
Details
Bug 1290958 tracks implementing the NavigationPreloadManager
API. This will introduce a NavigationPreloadState
associated with each ServiceWorkerRegistration
. This state specifies if the browser will perform a "preload request" for navigation requests intercepted by the registration's active worker; a "preload response" will be available to the active worker in its fetch handler. This state also specifies the value of the Service-Worker-Navigation-Preload
HTTP header included in the preload requests.
Updated•6 years ago
|
Updated•3 years ago
|
Updated•1 year ago
|
Comment 1•1 year ago
|
||
Hello Eden, it looks like Perry wanted this information visible in DevTools, but it's not really clear how.
Would you have an idea about it? Is this not relevant anymore?
Comment 2•1 year ago
|
||
I closed the bug since the bug description only mentioned something had been implemented.
I think this is not very meaningful for developer debugging. Developers know if the navigationPreload is on or not. In addition, the request will have a "Service-Worker-Navigation-Preload" header to inform the developers that the ServiceWorker performs the feature. Therefore, I would like to keep this as "Closed." Once we have more specific debugging features on ServiceWorker, we can consider adding this back some where.
But maybe I am wrong, let me know if you have any thoughts; thank you.
Description
•