[whatwg/xhr] Spec requires firing at least two "progress" events; browsers do not. (#318)

Example: https://boom-bath.glitch.me/xhr-small-chunks.html

The spec requires firing one as part of _processResponse_, and one as part of "handle response end-of-file". However, browsers only fire a single one.

As far as I can tell, they avoid firing the one in "handle response end-of-file" if the number of bytes hasn't changed. /cc @ricea in case he can make more sense of Chromium's implementation than I can.

-- 
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/318