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 12199 - 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
Summary: Need to test the URL-encoded form data algorithm when the charset is ISO-2022...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (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: needs testcase
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-27 05:22 UTC by contributor
Modified: 2011-09-27 19:10 UTC (History)
8 users (show)

See Also:

Attachments

Description contributor 2011-02-27 05:22:59 UTC 
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
Comment 1 Ian 'Hixie' Hickson 2011-05-05 08:11:27 UTC 
Do you have a test case demonstrating how UAs handle this today?
Comment 2 Ian 'Hixie' Hickson 2011-06-09 06:16:42 UTC 
Anyone have any suggestions on how to test this?
Comment 3 Michael[tm] Smith 2011-08-04 05:01:47 UTC 
mass-moved component to LC1
Comment 4 Ian 'Hixie' Hickson 2011-09-27 19:09:14 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: I hope this is what is needed.
Comment 5 contributor 2011-09-27 19:10:21 UTC 
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