Closed Bug 42329 Opened 24 years ago Closed 24 years ago

Address completion is too fast and completely messes up Japanese input into Address fields

Categories

(MailNews Core :: Composition, defect, P2)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: momoi, Assigned: bugzilla)

References

Details

(Whiteboard: [nsbeta2+]ETA:7/17 Fix in hand)

** Observed with 6/12/2000 Win32 build **

Problem Description:

When the address completion opiotn in ON (which is the default pref
status), and when you try to use Japanese input method editor (IME)
in the Address fields of new mail composer, it totally messes up
IME input status. 
For exmaple, 

1. Type "toukyou", 

2. You are supposed to see first TO U KYO U in Hiragana, 

3. The input in 2 then can be converted to Chinese characters representing 
   Tokyo when you press the space bar and choose one of the offered 
    selections for this pronunciation.

This is the normal input procedure for these 2 characters in Japanese.
Let's say that you have an Address Book entry containing "Tokyo" in
Chinese characters, you will never get this address completed in
the Addressing field because auto-completetion is set so fast
that the Japanese IME is never given a chance to even wait for 
the use-initiated conversion in step 3 above. 
Instead, it resolves the Address to "TO U KYO U"@domain.com.

This is basically auto-completion intruding on the work
of Japanese IME and disabling an important input function
in Addressing fields. 

Japanese users expect to be able to auto-complete using Japanese
names. This is totally impossible now.

J-F knows what to do with this bug as he and I talked about a possible
solution.
I'm nominating this bug for nsbeta2 because there is no way we can do
Japanese without AddressBook auto-completion.
Blocks: 38342
Keywords: nsbeta2
QA Contact: lchiang → momoi
Summary: Address completion is too fast and messes up Japanese input into Address fields → Address completion is too fast and completely messes up Japanese input into Address fields
Scott P., is J-F in work mode these days? If not, please find 
someone to fix the bug for M17. ftang also is aware of this bug.
Severity: normal → critical
Putting on [nsbeta2+] radar for beta2 fix. 
Whiteboard: [nsbeta2+]
Accepting. I am back to work...
Status: NEW → ASSIGNED
Priority: P3 → P2
Target Milestone: --- → M17
Momoi, I have already modified the autocomplete widget to not autocomplete if 
the text field as a specific attribute set. What we need to do now is to set 
this attribute every time IME take the control. Who could do that? who should I 
contact?
I've already copied ftang and nhotta on this and so I gather
the other person who should look at this is Joe, jfrancis.
Joe, can you help?
I can help.  I'll need to be filled in by ducarroz on the details of what he 
needs.  
Whiteboard: [nsbeta2+] → [nsbeta2+]ETA:7/14
i have implmented an nsIEditorObserver interface and added support for it to the 
editor; and changed the gfx text frame code to use nsIEditorObserver rather than 
nsIDocumentObserver.  The result should be only one oninput message per user 
action, and no oninput events from ime until the ime is committed.
Ok, Joe I myself have a version that of autocomplete that works fine with IME. 
We will check in our stuff either during the weekend or Monday.
Whiteboard: [nsbeta2+]ETA:7/14 → [nsbeta2+]ETA:7/17 Fix in hand
I've just checked in the editor and layout changes needed for this.  when 
ducarroz checks in autocomplete.xml, it should be all done.
I have checked in my part too.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
** Checked with 8/1/2000 Win 32 M17 build **

Now the address completion is  no longer intruding into 
Japanese IME process before the IME commit is completed.
This makes it possible for Japanese input to be entered
and then auto-completion to begin. 
Marking the fix verified as fixed.
Status: RESOLVED → VERIFIED
No longer blocks: 78270
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.