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

So, we agreed on https://github.com/w3c/ServiceWorker/issues/1167#issuecomment-350251122, right?

For `request.isReloadNavigation`, it seems we can reference [reload-triggered navigation](https://html.spec.whatwg.org/#reload-triggered-navigation) from the navigate algorithm, and set the corresponding boolean state (which needs to be added) of the request to relevant value. Maybe it'd be nice if we could define the reload-triggered navigation concept a little more concretely.

For `request.isHistoryNavigation`, we don't have any definition that collectively refers to history navigations yet. It seems we can add the history-triggerd navigation or something like that in [traverse the history](https://html.spec.whatwg.org/#traverse-the-history) algorithm.

If we want to specify it by introducing some concrete states, we will need to pass some additional arguments or flags to the navigate algorithm as the request is created inside of the navigate.

@annevk, do you have any other ideas?

-- 
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-361570347