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

Good points. We do have some discussion around that [right now](https://github.com/WICG/priority-hints/issues/11), but ultimately it seems reasonable to expose it. Main thing we're worried about now is a hint's effects taking place twice. For example, the UA defers sending `importance=low` requests to the SW because of the developer intention, then the same deferring takes place again when sending from the SW => actual network. This isn't really related to exposing the attribute or not, but I guess application code could do some extra playing around with the scheduling of a request if it were exposed.

If welcomed, I can start working on HTML and Fetch Standard PRs for this. HTML Standard issue is filed here (https://github.com/whatwg/html/issues/3670) for reference.

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