Closed Bug 28029 Opened 25 years ago Closed 25 years ago

IME-Japanese chars input timing problem

Categories

(Core :: Internationalization, defect, P5)

x86
Linux
defect

Tracking

()

VERIFIED WONTFIX
Future

People

(Reporter: teruko, Assigned: tajima)

References

()

Details

(Keywords: platform-parity)

I found this problem when I tried to verify the bug 24464. Same procedure to 24464. Steps of reproduce 1. Go to the above URL 2. Turn on IME (Kinput2) in linux 3. In Name field after Customer ID field, type 3 Japanese characters 4. Use Backspace key (hit backspace key 3 times) to delete these 3 Japanese characters 5. Type Japanese characters again If you do steps #4 and #5, and you type Japanese characters quickly, the uncommitted characters sometimes are displayed the wrong place. After you committed the characters, they are displayed in the correct place. Tested 2000021608 Linux build.
This is because we use a timer to update the XIC spot location. Mark this bug as M20.
Status: NEW → ASSIGNED
Target Milestone: M20
Keywords: pp
Summary: [PP] IME-Japanese chars input timing problem → IME-Japanese chars input timing problem
tajima-san, Can this be reassigned to you?
Assignee: ftang → tajima
Status: ASSIGNED → NEW
Target Milestone: M20 → ---
Reassigned to tajima and cleared TM of M20 for reevaluation.
Status: NEW → ASSIGNED
Change priority to P5 as on-the-spot inputstyle is used as default in Japanese XIM and it makes the problem apparently fixed.
Priority: P3 → P5
Should we mark this as M20 ?
Target Milestone: --- → M20
won't fix. OntheSpot is stable now.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
Target Milestone: M20 → Future
Verified.
Status: RESOLVED → VERIFIED

Hi Team,
Please find the below details.

Contact Number : 7758010680
Employee Id : 0971
Personal Email id: dineshjadhav98@gmail.com
date of joining : 12/09/2022
Designation : Sr. Data Analyst
location : Bangalore
Reporting Manager Name : Shrenik Sethi
Reporting Manager contact: 9168419966

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