Re: [whatwg/fetch] Consider splitting `document` into `document` and `nested-document`. (#755)

The idea of exposing the header to service workers sounds interesting.

My initial thought is what'd be a downside of maintaining the target member? The values of the destination look more like what the request's resulting resource kind would be. If we split them, there seems to be quite a few places that need some clarification. E.g. "A navigation request is a request whose destination is "document" **or "nested-document"**, etc.

> Do you mean resultingClientId? You won't be able to look at any information about that client until after the fetch completes, right?

Yes.

-- 
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/755#issuecomment-396337199