[Webkit-unassigned] [Bug 36156] XHR 'progress' event code assumes wrongly that expectedLength >= 0

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Mar 17 12:20:48 PDT 2011


https://bugs.webkit.org/show_bug.cgi?id=36156


Glenn Maynard <glenn at zewt.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |glenn at zewt.org




--- Comment #2 from Glenn Maynard <glenn at zewt.org>  2011-03-17 12:20:48 PST ---
I take it this is why I'm seeing e.total == 4294967295 in XHR onprogress events from chunked sources (on 32-bit systems).  http://zewt.org/~glenn/test-webkit-xhr-progress-chunked/

According to Progress Events, "maximum" should be left unchanged when the length of the HTTP entity body is unknown, which means it retains the initial value of zero.  FF4 follows this behavior.  http://dev.w3.org/2006/webapi/progress/#firing-events-using-the-progressevent-in

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list