Re: [whatwg/fetch] Copy priority so service worker pass-through requests don't lose it (#785)

> Maybe pass the original request in the init object of Request() and copy its priority or something like this?

Adding a new property to RequestInit would likely be a separate discussion/PR. One ambiguity with that is: which input request properties would be preferred in the following: `new Request(requestA, {request: requestB})`? Might make the spec a little weird too, but again, separate conversation.

> Maybe considering the request destination when assigning a new priority could help also.

This is what Chrome does (among other things) (and I suspect most browsers do) when resolving the actual priority of a request. Ultimately a goal of mine to standardize priorities more thoroughly; I don't know much of this will extend to the actual resolution of these priorities, or if it'd be better to just standardize different priorities associated with destinations and have some place saying "Let _steps_ be some implementation-provided steps to further influence priority _p_. Run _steps_ given _p_". But that is also a discussion with a more global effect (IMO a necessary a long-term one!).

-- 
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/pull/785#issuecomment-412065786