When a search is completed from the location bar, the text in the status bar changes to 'Resolving host' and then a variable - in this case the search word(s). If the search string contains extended characters they are now incorrectly displayed in the status bar. i.e. they appear corrup steps to repro: 1. In the Location bar type in a word that contains extended characters i.e. M�«änich 2. Click on Search 3. Note the text in the status bar

cc to IQA

Switching qa contact to jonrubin.

Actually I input a Japanese or Chinese characters in URL location bar then press the "enter", the status bar will appears garbage after the string "Resolving host". - I saw it on both Win2k-CN and WinXP-Ja with today's branch build. Should we change to "unable to handle non-Ascii characters" in Summary? Not reproduce on Mac and Linux.

Changing summary accordingly to Yuying's suggestion.

I have another case: If I open a file which saved under a non-ascii(Japanese, chinese ..etc) folder or file name though browser File | Open File, then the status bar will display garbage as well, I saw it on Win2k-CN, Mac9.0-Ja and RedHat6.2-Ja, but on WinME-Ja and WinXP-Ja, the non-ascii path / file name will show number code like: %C8%D5%B1%BE. Change Platform to All.

Encoded string is displayed as "???" in status bar. Maybe this is the same problem. http://dmoz.org/World/Japanese/%a5%b3%a5%f3%a5%d4%a5%e5%a1%bc%a5%bf/%a5%bd%a5%d5%a5%c8%a5%a6%a5%a7%a5%a2/%a5%a4%a5%f3%a5%bf%a1%bc%a5%cd%a5%c3%a5%c8/%a5%d6%a5%e9%a5%a6%a5%b6/Mozilla/

*** Bug 94803 has been marked as a duplicate of this bug. ***

move to jbetak and mark m9.4

Per Selmer suggestion, I am doing this myself. Moving nsbranch+ designation from the Status Whiteboard to Keywords.

mass change, switching qa contact from jonrubin to ruixu.

remove nsbranch+ keyword. move to m0.9.6

nsbranch- since Frank moved it to 0.9.6

pushing our a bit and accepting...

jbetak's contract is up. Bulk move bugs to ftang

give to nhotta to research

The test data in comment #6 works when the document charset is set to "EUC-JP". The problem is the original report requires IDN (International Domain Name) support.