[Bug 23348] The loaded property doesn't make sense when the body is compressed

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

--- Comment #10 from Marcelo Volmaro <mvolmaro@hotmail.com> ---
Boris: I get that, and that's what I understand. But I can't believe that 4
different browser makers (Opera, Mozilla, Apple and Google) agreed on disagree
with the specifications. So, either the specifications are not clear, or I
really don't know what to think about these companies. I even can understand
that Apple/Google may have the same behavior, as they started from the same
codebase. But not from Opera (and I'm talking about Opera 12, with the old
Presto engine) and/or Mozilla.

I see two paths here: 
- One where the content is sent uncompressed: this works as expected on all
browsers.
- One where the content is sent compressed (gzip/deflate, it doesn't matter):
this is not working as expected, but all browsers agreed on not working as
expected :)

I really don't care if the total/loaded is calculated from the number of
transferred bytes or from the size of the uncompressed body (that may/may not
be the same as the number of transferred bytes). I believe it would be easier
if they are calculated from the number of transferred bytes, so you don't need
to know the uncompressed size beforehand. And I believe that is what needs to
be clarified on the specifications.

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

Received on Wednesday, 25 September 2013 21:04:04 UTC