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 10461 - This algorithm needs more detail on how the data is to be actually encoded. E.g. does it depend on the document encoding, etc.
Summary: This algorithm needs more detail on how the data is to be actually encoded. E...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-27 13:03 UTC by contributor
Modified: 2010-10-12 00:10 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-08-27 13:03:27 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#multipart/form-data-encoding-algorithm

Comment:
This algorithm needs more detail on how the data is to be actually encoded.
E.g. does it depend on the document encoding, etc.

Posted from: 213.236.208.22 by annevk@opera.com
Comment 1 Ian 'Hixie' Hickson 2010-09-25 17:43:00 UTC 
Could you elaborate? What more information? Can you give an example of something that is ambiguous?
Comment 2 Anne 2010-09-26 09:31:04 UTC 
Basically, multipart/form-data format is very generic. For interoperability HTML5 should detail how the format is being used. (Or we should just take over the definition of that format entirely, as it is rather vague.)

If the document the <form> is in is encoded as windows-1252 will text fields be represented using text/plain;charset=windows-1252 or is text/plain;charset=utf-8 ok too? Or is the charset parameter left out by user agents?
Comment 3 Ian 'Hixie' Hickson 2010-09-29 07:44:49 UTC 
I was really hoping not to have to pull in that whole spec here and not to have to provide a replacement for that spec either...
Comment 4 Ian 'Hixie' Hickson 2010-09-30 19:37:06 UTC 
I guess I'll do some testing and work out what encoding browsers use when you change the document encoding and when you change accept-charset.
Comment 5 Ian 'Hixie' Hickson 2010-10-12 00:08:32 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: see diff given below
Rationale: Concurred with reporter's comments.

If I missed anything please file specific bugs with either test cases demonstrating the interoperable behaviour you want specced, or specific URLs of pages that depend on behaviour that doesn't match what the spec says.
Comment 6 contributor 2010-10-12 00:10:35 UTC 
Checked in as WHATWG revision r5600.
Check-in comment: Redefine how we interact with RFC 2388 (multipart/form-data) in submission
http://html5.org/tools/web-apps-tracker?from=5599&to=5600