- From: Anne van Kesteren <notifications@github.com>
- Date: Wed, 30 Nov 2022 23:36:16 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 1 December 2022 07:36:29 UTC
@annevk commented on this pull request. > @@ -7346,6 +7357,10 @@ constructor steps are: <li><p>If <var>init</var>["{{RequestInit/signal}}"] <a for=map>exists</a>, then set <var>signal</var> to it. + <li><p>If <var>init</var>["{{RequestInit/priority}}"] <a for=map>exists</a>, then use + it appropriately in setting <var>request</var>'s <a for=request>internal priority</a> + to an <a>implementation-defined</a> object. But this is a subset of what the fetch algorithm takes into account. Is that what we want? An alternative might be that the fetch algorithm also has a branch when internal priority is an implementation-defined object already and then modifies it to take into account potentially changed signals. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/1523#pullrequestreview-1200490971 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/pull/1523/review/1200490971@github.com>
Received on Thursday, 1 December 2022 07:36:29 UTC