Re: [whatwg/fetch] Introduce {reload, history, submission}-navigation flags (#685)

wanderview 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.

In general I think any field that is added to `Request` must be stored in cache API.  At least that is what we currently do and I think it would be unexpected for `cache.keys()` to return something that differs from what was passed to `cache.put()`.

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