Closed
Bug 594032
Opened 14 years ago
Closed 14 years ago
Lack of progress events when sending FormData in XMLHttpRequest
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 311425
People
(Reporter: apajaron, Assigned: smaug)
Details
Attachments
(1 file)
4.13 KB,
application/zip
|
Details |
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0b4) Gecko/20100818 Firefox/4.0b4 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b4) Gecko/20100818 Firefox/4.0b4 (.NET CLR 3.5.30729) When trying to upload a file as multipart/form-data (as explained here: http://hacks.mozilla.org/2010/07/firefox-4-formdata-and-the-new-file-url-object/ ), the progress event won't fire. Instead, we'll get directly a load event when finished. Reproducible: Always Steps to Reproduce: Try to upload a file with attached code (needs server-side processing of the form). Actual Results: Progress bar goes directly from 0 to 100% Expected Results: Progress bar actually shows progression of the upload. It works fine on Chrome 6 and Safari 5.
Reporter | ||
Comment 1•14 years ago
|
||
![]() |
||
Updated•14 years ago
|
Attachment #472638 -
Attachment mime type: application/octet-stream → application/zip
Olli, would you have time to look at this? I would have thought that the normal progress events could would have handled this just fine.
Assignee: nobody → Olli.Pettay
Nominating for blocker, but needs confirmation before I'll marking blocking+
blocking2.0: --- → ?
Assignee | ||
Comment 4•14 years ago
|
||
My guess is that this has something to do with "@mozilla.org/io/multiplex-input-stream;1"
Assignee | ||
Comment 5•14 years ago
|
||
Or not...
Assignee | ||
Comment 6•14 years ago
|
||
Ah, this is a dup. The progress event listener must be (unfortunately) set before calling open (in Mozilla).
Assignee | ||
Updated•14 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•14 years ago
|
blocking2.0: ? → ---
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•