Closed Bug 429473 Opened 18 years ago Closed 16 years ago

Form data sometimes POSTed in wrong character set.

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: joh-hans, Unassigned)

Details

(Whiteboard: [CLOSEME 2010-09-15])

User-Agent: Opera/9.26 (X11; Linux i586; U; en) Build Identifier: I have experienced posting on various Swedish-language message boards, using the iso8859-1 character set that sometimes when I (or someone else) have posted using FireFox, non-ASCII characters have sometimes been posted as garbled multi-byte sequences. Web page header specifies character set to be iso-8859-1. Quick translation (iconv) revealed that the posts were in utf-8. This occurs far from always, seemingly at random (maybe one in a hundred), and on multiple message boards. I have experienced it myself, and seen others post such messages. Reproducible: Couldn't Reproduce Steps to Reproduce: 1. 2. 3. The bug has been experienced with several versions of Mozilla Firefox in the last three years, so it is not new. Example web-based message boards where I have seen this happen: boards.theforce.net, www.starwars.nu The non-ASCII characters in Swedish are Å, Ä, Ö (å, ä, ö). Question: Are the character sets on these sites the same in HTTP header and HTML header? -- could the code in Mozilla Firefox check one or the other in different circumstances?
Reporter, are you still seeing this issue with Firefox 3.6.x or later in safe mode? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2010-09-15]
No reply, INCOMPLETE. Please retest with Firefox 3.6.10 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.