[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 #15 from Boris Zbarsky <bzbarsky@mit.edu> ---
> but how can the order matter? 

It matters because the way XHR in Gecko asks the network library for sane
progress events is via a boolean in the data it hands it when it starts the
network load.  That data can't change once the load is started.  So Gecko has
to decide inside send() whether it wants sane progress information or not.  If
not, then it'll still synthesize some sort of progress events based on how much
data it's gotten, but they won't be terribly useful, as you discovered.

> I don't think this detail affects my suggestion to use the post-C-E values
> instead of the in-between-CE-and-TE values.

There is no sane way to use the post-C-E value for "total".  You don't know
what that is until the load is done.

Might as well spec "total" as always returning 0 and lengthComputable as always
being false be done with it: that's all UAs will _ever_ be able to do for C-E
cases if you want post-C-E values.

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

Received on Thursday, 26 September 2013 02:52:15 UTC