[Bug 25587] Be more clear that progress events are about bytes being transferred

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25587

Thomas Wisniewski <wisniewskit@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |annevk@annevk.nl,
                   |                            |wisniewskit@gmail.com
              Flags|                            |needinfo?(annevk@annevk.nl)

--- Comment #14 from Thomas Wisniewski <wisniewskit@gmail.com> ---
In the interest of settling long-standing issues related to progress events, I
would recommend just changing the web platform tests to match the spec wording
as precisely as possible. This will cause some browsers to fail tests they're
currently passing for seemingly trivial reasons, but the spec now seems
reasonable (and reasonably clear) about which events to fire and which loaded,
total, and lengthComputable values to send in those events. For instance:

- no final progress events will be fired in the error case, just the
error/loadend events with 0 values (as these events add no real value and are
not currently fired by user agents anyhow).

- progress events will set loaded and total to the raw bytes transferred, not
the values after decoding (this is info the user cannot compute on their own,
whereas they will always know the decoded size upon completion).

- upload.loadstart will set the total and loaded=0 and lengthComputable=true
(since the total ought to be known by that point, although some UAs currently
fire 0/0/false).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Saturday, 17 September 2016 13:22:48 UTC