- From: Jake Archibald <notifications@github.com>
- Date: Mon, 26 Mar 2018 13:46:05 +0000 (UTC)
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 26 March 2018 13:46:31 UTC
jakearchibald commented on this pull request. > @@ -1162,6 +1162,18 @@ Unless stated otherwise, it is "<code>basic</code>". <p>A <a for=/>request</a> has an associated <dfn export for=request id=done-flag>done flag</dfn>. Unless stated otherwise, it is unset. +<p>A <a for=/>request</a> has an associated +<dfn export for=request id=reload-navigation-flag>reload-navigation flag</dfn>. Unless stated +otherwise, it is unset. + +<p>A <a for=/>request</a> has an associated +<dfn export for=request id=history-navigation-flag>history-navigation flag</dfn>. Unless stated +otherwise, it is unset. + +<p>A <a for=/>request</a> has an associated +<dfn export for=request id=submission-navigation-flag>submission-navigation flag</dfn>. Unless stated +otherwise, it is unset. Tri-state so it can have an 'unset' value? Seems like it'd be less confusing to just store these values in the cache API, even though it isn't particularly useful. -- 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/685#discussion_r177095014
Received on Monday, 26 March 2018 13:46:31 UTC