Last Comment Bug 28019 - Form POST method fails with charset <> iso-8859-1
: Form POST method fails with charset <> iso-8859-1
Status: VERIFIED DUPLICATE of bug 27006
Product: Core
Classification: Components
Component: HTML: Form Submission (show other bugs)
: Trunk
: All All
P3 major with 3 votes (vote)
: ---
Assigned To: Frank Tang
: Vladimir Ermakov
: Andrew Overholt [:overholt]
Depends on:
  Show dependency treegraph
Reported: 2000-02-16 10:49 PST by Spiros Ioannou
Modified: 2000-12-15 18:37 PST (History)
4 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Description User image Spiros Ioannou 2000-02-16 10:49:32 PST
Form POST method fails when the charset is for example iso-8859-7.
By charset I mean the value of:
 <meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-7">
in the <head> </head> section

The problem may reside in the renderer because the page is displayed
instantly in 8859-1 encoding and then it is instantly reloaded in the
correct encoding without the post variables posted.

You can find an example there:
Enter something in the box and press submit. The value entered will normally
exist in the box after the submit, but not with mozilla. In my case the box
reappears empty. The problem dissapears if I remove the <meta ...charset=...>
tag from the html.

The php used is elementary. Follow the link to see the source.
This bug also exists in the solaris version, and existed in previous milestones.
The millestone tested is M13

At your disposal for further information,
Spiros Ioannou
Comment 1 User image karnaze (gone) 2000-02-16 11:00:47 PST
Reassigning to Warren.
Comment 2 User image Warren Harris 2000-02-16 13:30:20 PST
=> valeski
Comment 3 User image Judson Valeski 2000-02-24 13:26:31 PST
over to ftang.

Frank, It looks like we're not sending the charset back to the server

I suspect this is that fun bug where we're damned-if-we-do or
Comment 4 User image Frank Tang 2000-02-25 12:56:58 PST
valeski- No, this is not realted to the sending charset back problem. 
The rendering issue is about meta reload. It should be gone now.
>The value entered will normally exist in the box after the submit
This is related to the bug that we currently do not remember form value after 
post (see bug 13537) and non ASCII string currupted when they try to remember it 
(see bug 29154 22580)
Comment 5 User image Frank Tang 2000-02-25 13:08:57 PST
sorry, my early analysis is wrong. The problem is not related to those bug. It 
is because we do a meta reload which clean up the setting. If user set the 
default charset to ISO-8859-7 then the problme go away. This bug is because we 
do a reload when we hit the meta tag. Maybe we should do a "Peek" in the first 
block to reduce the chace of reload. 
Comment 6 User image Frank Tang 2000-03-07 16:48:26 PST
We should consider adding "peeking" code into parser to get charset info to 
reduce the need of meta charset reload.
Comment 7 User image Frank Tang 2000-03-14 21:22:37 PST
jbetak, can you help to fix this ?
Comment 8 User image Frank Tang 2000-03-14 21:23:40 PST
sorry- wrong bug.
Comment 9 User image Frank Tang 2000-04-04 17:37:38 PDT
Mark this M19. Move the serverity to normal since it only break this test case.
Comment 10 User image Jonas Nagel 2000-05-06 04:27:37 PDT
I just got a "complaint" today, and it seems it doesn't only break the test 
case, because this guy brought another case, and I think there will be yet many 
more forms which will be affected, namely really all which are not with 
ISO-8859-1 Charset...


[raising severity to major]
Comment 11 User image Frank Tang 2000-06-05 23:40:56 PDT
form posting and charset conversion / handling issue. Reassign to jbetak and cc 
Comment 12 User image (away - not reading bugmail) 2000-06-27 18:08:16 PDT
reassigning to ftang for resource reallocation
Comment 13 User image Frank Tang 2000-06-28 00:58:26 PDT
assign untill find new owner for form handling
Comment 14 User image Mirek Hankus 2000-07-03 07:41:35 PDT
In my case Mozilla (2000070220) does not POSTs values at all.
Changing method from POST to GET resolves problem, but this
is not right way to solve this problem.
Comment 15 User image fig\tree 2000-07-06 21:22:58 PDT
The meta charset reload is the problem here, it doesn't repost form data.

*** This bug has been marked as a duplicate of 27006 ***
Comment 16 User image Vladimir Ermakov 2000-09-25 14:42:05 PDT
Updating QA contact.
Comment 17 User image Vladimir Ermakov 2000-09-27 11:25:07 PDT
Verifying duplicate

Note You need to log in before you can comment on or make changes to this bug.