** Observed with 10/26/99 (1999102608) Win32 M11 build ** I also observed this problem with today's Linux build. I suspect that this is cross-platform. This is somewhat similar to what I see described in Bug 15784 but cannot tell completely from that description that this is the same bug. The problem should affect other similar widgets. Maybe this is a known bug. In that case, I'd appreciate someone pointing me to that bug. Here's the problem description: 1. Open a new mail composer window. 2. Turn on Japanese IME. 3. Click into the Subject field. 4. Start typing something in Japanese. 5. Note that no input is visible in the field. 6. After step 4 is taken, i.e. some IME key actions have been performed while the focus is in the Subject field, all subsequent input will fail. It's as if the Subject field has become completely off-limits to any further input, ASCII or Japanese, or whatever. Other fields such as "TO:" field, or body text input areas area are not affected by this. (Note: You do;'t have to commit any charcters to induce this problem. Just some IME key actions while the focus is in the Subject field.) Workaround: There is a workaround. That is, to input a single ASCII character before tyring any input actions with the Japanese IME into the Subject field. Thereafter, you should experience no problem. You can even backtrack and delete the ASCII character after the Japanese input is done and that would be OK.
I'm marking this as International Mail [Dogfood].
Seems like Joe should be on the cc list for this considering he just checked in changes to the editor's IME code.
Note that there was another bug which said that Japanese IME actions in **any** input field, "To:, CC:...", Subject, and Body Text, causes Mozilla to freeze. That problem seems to be gone now. At least I have no problem starting with Japanese input (without any ASCII character at the beginning) into "To:" line and Body Text. This problem is restricted to the Subject line.
should be fixed by my Tuesday checkin. please verify
** Checked with 10/27/99 Win32 build (1999102708) ** Thank you, jfrancis. Yes indeed, this bug has been fixed. No more workaround needed. We can now start inputting into the Suject field starting with a Japanese character. As of the above build, I'm marking this fix verified.