Re: [whatwg/xhr] Clarify if `ProgressEvent.loaded` should indicate the size of compress, or uncompressed, data (Issue #388)

cutiful left a comment (whatwg/xhr#388)

@annevk is it still true that Firefox is correct? It seems like https://github.com/whatwg/xhr/pull/313 would change that. As far as I understand, transmitted bytes on body referenced the compressed length here:
```html
 <li><p>Let <var>transmitted</var> be <var>response</var>'s <a for=response>body</a>'s
 <a for=body>transmitted bytes</a>.
```

But in the new version, it uses the length of received bytes:
```html
 <li><p>Let <var>transmitted</var> be <var>xhr</var>'s <a>received bytes</a>'s
 <a for="byte sequence">length</a>.
```

Which, if I'm not mistaken, are set by the HTTP-network fetch algorithm after handling codings. Otherwise, the XHR specification would have to handle codings as well, so I believe my understanding is correct that this is decompressed length.

That makes the Chrome behavior the correct one. And I think it also means that the progress event is potentially fired with mismatching lengths (decompressed loaded and compressed total).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/xhr/issues/388#issuecomment-3369074568
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/xhr/issues/388/3369074568@github.com>