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

Thanks for the cc! Since this thread's birth, this idea has been embodied in [Priority Hints](https://github.com/WICG/priority-hints), and is currently being discussed at https://github.com/whatwg/html/issues/3670 to see if we can get it in HTML/Fetch. @wanderview we're currently going with `low`, `auto`, and `high` `importance` values, which serve as a hint to a resource's intended priority. If you'd like to chime in there a bit that'd be awesome, as we're trying to gauge interest from other browsers.

I know that [priority](https://fetch.spec.whatwg.org/#concept-request-priority) as request concept already exists here, but how do we feel about having another concept `importance`, which is potentially exposed? Here are some questions/thoughts:

 - Would it be too confusing having both `importance` and `priority` concepts on a Request object?
 - I know that exposing `priority` was discussed here. My thoughts are that `priority` might be a little too specific to expose here, not to mention it might be computed later than the request is made (though an estimation or baseline could be exposed instead I guess). I'm more in favor of exposing `importance`, which would default to `auto` unless developer-specified. I know @yutakahirano was a big fan of not exposing Request.importance in Chrome's initial implementation, I believe for ease of adoption, but if we think it would be nice to expose this, as @wanderview mentioned exposing `priority`, that could work. Thoughts?

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