Re: [whatwg/xhr] final readystatechange (readyState === 3) (#161)

Does it make sense to have vague statements, such as

- Let read be the result of reading a chunk from response’s body’s stream with reader.
 - When read is fulfilled with an object whose done property is false and whose value property is a Uint8Array object, run these subsubsubsteps and then run the above subsubstep again:
   1. Append the value property to received bytes.
   1. If state is headers received, then set state to loading and fire an event named readystatechange.
   1. Otherwise, fire an event named readystatechange, but in the following manner:  The user agent may delay or coalesce multiple progress events up to 50ms, as long as [state](https://xhr.spec.whatwg.org/#concept-xmlhttprequest-state) is _loading_.
   1. Fire a progress event named progress with response’s body’s transmitted bytes and response’s body’s total bytes, but in the following manner:  The user agent may delay or coalesce multiple progress events up to 50ms, as long as [state](https://xhr.spec.whatwg.org/#concept-xmlhttprequest-state) is _loading_.

?

-- 
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/xhr/issues/161#issuecomment-379942799