Re: [whatwg/fetch] Consider to add "resolveAtIdleTime" to RequestInit (#821)

> Is there a reason we can't define a single API/developer-signal to implement both network priority and response handling?

I cannot think of a reason to not tackle both the problems (other than scope), makes sense to consider both aspects. However the response handling priority is a bit different: it needs a way to pass a  priority (that won't always necessarily be the same as fetch priority), that can potentially be updated (eg. something was fetched preemptively to prepare next screen, but now the user has explicitly requested it or vice versa). 

Ability to specify priority for fetch promise resolution (and something for xhr) makes sense to me.



-- 
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/821#issuecomment-434010124