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

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

--- Comment #6 from Takeshi Yoshino <tyoshino@google.com> ---
(In reply to Olli Pettay from comment #5)
> (In reply to Takeshi Yoshino from comment #3)
> > So, my gut feeling is we should remove "fire a progress ProgressEvent" step
> > from the algorithm but make "fire a _event_ progress ProgressEvent" and
> > maybe "fire a loadend ProgressEvent" to use the last loaded/total value.
> > 
> > WDYT?
> 
> I don't understand this part.

Me too after two weeks... I also found a typo. Rewrote:

I suggest that:
- we remove "fire a progress ProgressEvent" step
- have the "fire a _event_ ProgressEvent" step to use the last loaded/total
value than 0/0
- have the "fire a loadend ProgressEvent" step to use the last loaded/total
value than 0/0

Then:
a) we don't dispatch the misleading progress ProgressEvent (a progress
ProgressEvent with positive value looks indicating the loading is still
successfully going without any error. we should avoid dispatching such an
event)
b) we can know at which point of loading the error occurred. Maybe useful for
debugging. As we'll see a ProgressEvent named error/abort/timeout, it's not
misleading like (a)

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

Received on Tuesday, 26 August 2014 07:44:56 UTC