Re: [whatwg/fetch] consider exposing and allowing script to set Request priority (#436)

@wanderview How does that IDL sketch reconcile with https://fetch.spec.whatwg.org/#fetching ? That is, that 'priority' is a user-agent defined object, but the IDL sketch seems to make it a specific set of values (no longer UA defined)

In particular, I'm thinking about the Note in Step 5
> The user-agent-defined object could encompass stream weight and dependency for HTTP/2, and equivalent information used to prioritize dispatch and processing of HTTP/1 fetches.

At least in Chrome, the low/normal/high is not a priority system we're happy with, and certainly not with exposing, at least historically speaking. Even weighting numeric priorities has caused a host of issues with H/2 processing, and we're trying to move away from that. I'm not sure how Firefox is handling that, but I thought @mcmanus had implemented a much more nuanced priority/dependency tracking already.

-- 
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/issues/436#issuecomment-267229016