Re: [w3c/ServiceWorker] Proposal: FetchEvent.navigationLoadType (#1167)

I guess my only concern here is that we already have some overlapping members on Request:

* evt.request.mode === 'navigate' for these cases
* evt.request.type and evt.request.destination have also cover aspects of how/why the browser initiated the load

Should `navigationType` be part of the Request object instead of FetchEvent?

Is this something browsers might usefuly do so something with in the pass through case `e.respondWith(fetch(e.request))`?  If we put this info on the request it would get passed through, but if its on FetchEvent it is not passed through.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1167#issuecomment-315085435