Add note about ProgressEvent.loaded
reporting different values depending on the browser
#32781
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add note about
ProgressEvent.loaded
reporting different values depending on the browserIn Firefox,
loaded
is the size of the compressed data; in Chrome, it's the size of the decompress data. I would have loved to find sources for this, but the only thing I could find is that the RFC doesn't specify which value it should be! Browsers implement it differently.I also did some rephrasing to make all sentences similar.
Motivation
Make developers aware that the values of
loaded
might be different for their users.Additional details
loaded
, shows a total of1345276
at the end.loaded
, shows a total of1017454
at the end.