Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447)

> Is that `.fetchObserver` associated to the navigation preload?

I'm not sure what you mean by "navigation preload", but the fetch that's being observed by `event.fetchObserver` (in the way I'm modeling it) is the "fetch" that *whatever* dispatched the request is seeing. So, for instance, when a script on the page calls `fetch()`, or the UA dispatches a request for `style.css` based on a `<link rel="stylesheet">` in the page, from those two points of view, they have "initiated a fetch", even if there may not be any such fetch *on the wire*: they're dispatching a fetch *to the ServiceWorker*, who may then respond either with a fetch on the wire, *or* a fetch from cache (or a generative response from a function, or something like that).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/447#issuecomment-275811352