This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 12122 - AJAX File Uploads
Summary: AJAX File Uploads
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-18 18:05 UTC by Tab Atkins Jr.
Modified: 2011-08-04 05:11 UTC (History)
6 users (show)

See Also:


Attachments

Description Tab Atkins Jr. 2011-02-18 18:05:30 UTC
(This bug was split out from
<http://www.w3.org/Bugs/Public/show_bug.cgi?id=11796>.)

3)
AJAX file uploads
-----------------------
HTML5 should officially support AJAX based file uploads. Current workarounds
exist like submiting form to an
iframe but these are just hacks. What I am saying is that the XMLHttpRequest
object should have a property like
file which is an array and the IDs of the file upload input type can be stored
in this array. When the submit method is
called, the files are uploaded.
Also, HTML5 should provide certain file upload related events - 4 events are
suggested below
a )onuploadbar - This event is raise each time a certain amount (bar) of
percentage of file is uploaded. E.g. event is
raised each time 10% of file is uploaded.
b )onuploadcomplete - This event is raised when all files are uploaded
successfully
c )onfilecomplete - For multiple file uploads, this event is raised for each
file that has been successfully uploaded
d )onuploadfailed - This event is raised if any error occurs during upload
causing the upload to fail
Comment 1 Tab Atkins Jr. 2011-02-18 18:08:19 UTC
This is handled by XHR and FormData.
Comment 2 Maciej Stachowiak 2011-02-19 03:21:59 UTC
Not just FormData but also the ability to send a File object via XHR, and the xhr.upload object for upload progress events.
Comment 3 Ian 'Hixie' Hickson 2011-05-04 23:30:59 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: no spec change
Rationale: Already possible as per comment 1 and comment 2.
Comment 4 Michael[tm] Smith 2011-08-04 05:11:55 UTC
mass-move component to LC1