A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
FormData: Difference between revisions
| Line 17: | Line 17: | ||
Parse as multipart/form-data and populate FormData. Probably need to have a good definition of multipart/form-data first. | Parse as multipart/form-data and populate FormData. Probably need to have a good definition of multipart/form-data first. | ||
XXX: The HTML dirname feature seems to be one way only. Maybe the feature needs to be redesigned? | |||
XXX: If there is no name, imply "isindex"? | |||
==HTML Proposal== | ==HTML Proposal== | ||
Revision as of 12:42, 14 May 2012
Ideas around changing the FormData API.
- Populate FormData from the server. (multipart/form-data entity -> FormData)
- Get and manipulate FormData values.
FormData Proposal
- void append(name, value [, filename]) — normalize Blob [+ filename] to File since it always gets a filename
- void set(name, value [, filename]) — replaces *all* name entries
- void remove(name) — removes *all* name entries
- sequence<DOMString> getNames()
- sequence<DOMString> getValues(name)
XMLHttpRequest Proposal
responseType = "formdata"
Parse as multipart/form-data and populate FormData. Probably need to have a good definition of multipart/form-data first.
XXX: The HTML dirname feature seems to be one way only. Maybe the feature needs to be redesigned?
XXX: If there is no name, imply "isindex"?
HTML Proposal
Something like HTMLFormElement.populate(FormData) which updates all entries with the data from FormData. Maybe it should take a dictionary to indicate whether unaffected items should be cleared or retained.