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 11067 - Provide <form>-agnostic multipart/form-data encoding algorithm
Summary: Provide <form>-agnostic multipart/form-data encoding algorithm
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-15 16:34 UTC by Anne
Modified: 2011-08-04 05:16 UTC (History)
5 users (show)

See Also:


Attachments

Description Anne 2010-10-15 16:34:53 UTC
For FormData it would be great to have a <form>-agnostic multipart/form-data encoding algorithm. As input it should accept key/value pairs where each key is a DOMString and the associated value is one of DOMString/Blob/File. Encoding can be forced to UTF-8 for FormData though having to set it as parameter is no problem (might be good even so it is clear from the FormData specification).
Comment 1 Ian 'Hixie' Hickson 2011-01-11 20:55:10 UTC
Done. You just have to change two things in XHR: add "and with UTF-8 as the explicit character encoding" to the sentence that invokes the algorithm, and in the definition of FormData.appendData(), say that the type of the entry is "text" if the value argument is a DOMString, and "file" if it's a Blob (and if it's a Blob and not a File, say that its filename is the empty string).



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: see diff given below
Rationale: Concurred with reporter's comments.
Comment 2 contributor 2011-01-11 20:57:02 UTC
Checked in as WHATWG revision r5774.
Check-in comment: Provide a hook for the XHR spec.
http://html5.org/tools/web-apps-tracker?from=5773&to=5774
Comment 3 Michael[tm] Smith 2011-08-04 05:16:01 UTC
mass-move component to LC1