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

I'm a bit confused by how exactly the proposed fields in navigationInfo actually map to real-world events, especially "submit".  I'd like to verify my assumptions about the values for various use cases:

User hits the reload button in the browser: {reload:true, history:false, submit:false}
User focuses the omnibox and immediately presses enter: {reload:true(??), history:false, submit:true}
User types a new URL into the omnibox and presses enter: {reload:false, history:false, submit:true}
User hits back button to get to a page: {reload:false, history:true, submit:false}
Forward button: {reload:false, history:true, submit:false}
User clicks on a link to get to page: {reload:false, history:false, submit:false} (??)
Page is reloaded because user switched to that tab but Chrome had thrown it out of memory: {reload:true, history:true, submit:false} (??)

Honestly I think this API would be a lot simpler and easier to understand as something like an enum of actual user events rather than these three vague bools, but I'll take whatever I can get.

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