Re: [whatwg/fetch] Split 'document' destination into 'frame' and 'iframe'. (#948)

mikewest commented on this pull request.



> @@ -1567,13 +1573,13 @@ whose <a for=request>destination</a> is "<code>audio</code>", "<code>audioworkle
 "<code>object</code>" or "<code>embed</code>".
 
 <p>A <dfn export>non-subresource request</dfn> is a <a for=/>request</a>
-whose <a for=request>destination</a> is "<code>document</code>",
-"<code>report</code>", "<code>serviceworker</code>", "<code>sharedworker</code>",
-or "<code>worker</code>".
+whose <a for=request>destination</a> is "<code>document</code>", "<code>frame</code>",
+"<code>iframe</code>", "<code>report</code>", "<code>serviceworker</code>",
+"<code>sharedworker</code>", or "<code>worker</code>".

So, given that the potential resolution to the underlying question in https://github.com/whatwg/fetch/pull/948#issuecomment-543560997 puts the `embed` and `object` destinations into two categories (depending on the mode), what would you like me to do with these definitions ("navigation request", "non-subresource request"?

Should we leave them as they are in this patch, or do you want to include/excude requests with a `mode` of `navigate` as appropriate?

-- 
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/pull/948#discussion_r336862935