12199 2011-02-27 05:22:59 +0000 Need to test the URL-encoded form data algorithm when the charset is ISO-2022-JP and the value contains multiple characters in the non-default mode 2011-09-27 19:10:21 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#url-encoded-form-data needs testcase P3 normal --- 1 contributor ian annevk excors ian mike Ms2ger public-html-admin public-html-wg-issue-tracking zcorpan public-html-bugzilla oldest_to_newest 46078 0 contributor 2011-02-27 05:22:59 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/complete.html Section: http://www.whatwg.org/specs/web-apps/current-work/#url-encoded-form-data Comment: Step 4.4 "For each character ..." -> It must operate on a sequence of characters, not on a character. Otherwise it would generate overlong form when the encoding is stateful (e.g. consider ISO-2022-JP's escape sequences). Posted from: 113.197.157.219 48065 1 ian 2011-05-05 08:11:27 +0000 Do you have a test case demonstrating how UAs handle this today? 49363 2 ian 2011-06-09 06:16:42 +0000 Anyone have any suggestions on how to test this? 52470 3 mike 2011-08-04 05:01:47 +0000 mass-moved component to LC1 57431 4 ian 2011-09-27 19:09:14 +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: I hope this is what is needed. 57432 5 contributor 2011-09-27 19:10:21 +0000 Checked in as WHATWG revision r6592. Check-in comment: Try to make the application/x-www-form-urlencoded algorithm work even for ISO-2022-JP's crazy escape schemes. http://html5.org/tools/web-apps-tracker?from=6591&to=6592