264255 - Forms don't work with ISO-2022-CN

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Beirne Konarski]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041013 Firefox/0.10
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041013 Firefox/0.10

I worked with a web page developer whose page used the ISO-2022-CN Chinese
character set.  It turns out that form data does not get transmitted back to the
server with this character set.  Using the GET method, all that shows in the URL
is the equals sign, not the field name or contents.

Reproducible: Always
Steps to Reproduce:
1. Run script CGI included below.
2. Enter some text in the box
3. Submit.
4. Look at the URL  

Actual Results:  
The page reference will fail, but that isn't a problem.  The URL will have an =
without the field name beforehand or the contents afterwards.

Expected Results:  
The field name and contents should be in the URL.

CGI script to demonstrate the problem.  I don't have a handy public server to
demonstrate the problem from.


----------------------------------------------

#!/usr/bin/perl -T

use strict;

use CGI qw/:standard/;

print header(-charset => 'ISO-2022-CN'),
        start_html(-title => "A simple example");
print '<form action="bin/echo-form.cgi" method=get>

<p>This form uses the get method.

<p>Click the Submit query button.

<p><input type=text name=textinput value="Hello, world.">

<p><input type=submit>

<p>After you click the Submit query button, check the Location: box.

<p>The original URL should have the following string appended to it:

<p>?text_input=Hello%2C+world.

</form>',
        end_html;

Comment 1

[Beirne Konarski]

Attachment: This is the script I pasted into the original report.

This script produces a page with the ISO-2022-CN character set.

Comment 2

[Benjamin]

Attachment: Test html (uploaded as plain text)

I'm not sure how would be the best way to upload this file and ensure the
encoding is still correct so I've included it as text, html and binary.

Comment 3

[Benjamin]

Attachment: HTML version

Comment 4

[Benjamin]

Attachment: Binary version

Comment 5

[Benjamin]

Sorry I should have put the comment first:

I believe the issue in confined to just the Chinese character set I have an
unknown character set file (created by Xselerator XSL editor) that is causing a
similar issue, i.e.
<input type="submit" name="testInput">
would appear as
test.html?t=
instead of
test.html?testInput=
I've uploaded the test.html example attachment three times as I'm not sure of
format it should be in to keep the encoding.

Comment 6

[Benjamin]

That should have been
"I believe the issue is NOT just confined to just the Chinese character set - I
have an unknown character set file (created by Xselerator XSL editor) that is
causing a similar issue"

Comment 7

[Benjamin]

I also should have added my variant of this bug occurs with Windows XP

Comment 8

[Josh Myer]

This bug also affects ISO-2022-KR, confirmed under both FireFox and Mozilla on
Linux x86.

Repro:  Go to google.com, set your character encoding to ISO-2022-KR, and try to
search.  You'll see the behavior exactly as specified; no form elements are
passed on in the GET request.

(exact version: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050421
Firefox/1.0.3 (Debian package 1.0.3-2) )

Comment 9

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 10

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.