10461 2010-08-27 13:03:27 +0000 This algorithm needs more detail on how the data is to be actually encoded. E.g. does it depend on the document encoding, etc. 2010-10-12 00:10:35 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#multipart/form-data-encoding-algorithm P3 normal --- 1 contributor ian annevk ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 37997 0 contributor 2010-08-27 13:03:27 +0000 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 39362 1 ian 2010-09-25 17:43:00 +0000 Could you elaborate? What more information? Can you give an example of something that is ambiguous? 39460 2 annevk 2010-09-26 09:31:04 +0000 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? 39893 3 ian 2010-09-29 07:44:49 +0000 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... 40276 4 ian 2010-09-30 19:37:06 +0000 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. 40957 5 ian 2010-10-12 00:08:32 +0000 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. 40958 6 contributor 2010-10-12 00:10:35 +0000 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