Re: [whatwg/fetch] Add the Priority Hints changes to the fetch spec (PR #1523)

@annevk commented on this pull request.

The Request constructor is not correct:

* It copies priority rather than internal priority.
* When priority is given this is not taken into account. I suspect that when it's given we want to set request's priority to it and we want to set internal priority to null (so request's priority will be used upon fetching to initialize it). Or would we want to adjust internal priority instead in some manner so the existing prioritization information is taken into account?

> +  <p class=note>The <a>implementation-defined</a> object could encompass stream weight and
+  dependency for HTTP/2, priorities used in
+  <a href=https://datatracker.ietf.org/doc/rfc9218/>HTTP extensible priorities</a> for transports
+  where it applies (including HTTP/3), and equivalent information used to prioritize dispatch and
+  processing of HTTP/1 fetches.

```suggestion
  <p class=note>The <a>implementation-defined</a> object could encompass stream weight and
  dependency for HTTP/2, priorities used in <cite>Extensible Prioritization Scheme for HTTP</cite>
  for transports where it applies (including HTTP/3), and equivalent information used to prioritize 
  dispatch and processing of HTTP/1 fetches. [[!RFC9218]]
```

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1523#pullrequestreview-1199505019
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1523/review/1199505019@github.com>