[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 #16 from Glenn Maynard <glenn@zewt.org> ---
(In reply to Boris Zbarsky from comment #15)
> 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.

That's what I said:
> browsers would need to do is to ensure that total == 0 and lengthComputable
> == false if it doesn't know the size.


> 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.

Err, no.  It's only 0/false if C-E is in use, not always.  That's true for a
lot of smaller files (scripts, CSS), but probably uncommon for large files,
where it's most important to have the total (since large files are typically
internally compressed, eg. video and music).

If vendors are actually planning on fixing this to match spec, then leaving the
spec alone is fine.  It's a better end result, since progress bars will be
available more often.  But, with strong interop on the post-C-E behavior, I
wonder if it's worth the risk (of only some browsers changing, and ending up
losing the interop we have).

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

Received on Thursday, 26 September 2013 03:19:01 UTC