Closed
Bug 17916
Opened 25 years ago
Closed 25 years ago
IME bug - Caret does not move when type uncommitted text in over-the-spot IME style
Categories
(Core :: Internationalization, defect, P3)
Tracking
()
VERIFIED
FIXED
M15
People
(Reporter: teruko, Assigned: tajima)
References
()
Details
(Keywords: inputmethod)
When you type Japanese characters in form text area, Find filed of Find on This
page dialog, and Location bar, the caret does not move while you are typing.
Steps of reproduce
1. Go to above URL
2. Turn on kinput2 by Shift+Space
3. Try to type Japanese characers in the text field
The caret does not move the character by character while you are typing.
Tested 11-03-09 Linux build.
Updated•25 years ago
|
Assignee: ftang → tajima
Target Milestone: M12
Comment 1•25 years ago
|
||
the url invalide. Please put the right one there.
Reporter | ||
Updated•25 years ago
|
Reporter | ||
Comment 2•25 years ago
|
||
Sorry, I updated the right URL.
Comment 3•25 years ago
|
||
somehow I saw the caret move. DO you mean it does not move before you commit ?
or do you mean it does not move EVEN after you commit ?
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 4•25 years ago
|
||
In my environment today, kinput2 does not work well on textarea/textfield
widgets such as "Find On Page".
1. kinput2 status window come up with WM's decoration, but it should not.
2. I don't see any preedit window on text widgets.
Reporter | ||
Comment 5•25 years ago
|
||
Frank, I meant the caret does not move before I commit the characters. I tested this in 12-01-09 Linux build.
This still happens.
Reporter | ||
Updated•25 years ago
|
Summary: [PP]IME bug - Caret does not move while typing → [PP][BETA] IME bug - Caret does not move while typing
Not dogfood and there are many caret problems that won't be resolved in M12.
Moved to M13.
Target Milestone: M12 → M13
Updated•25 years ago
|
Assignee: tajima → ftang
Status: ASSIGNED → NEW
Target Milestone: M13 → M12
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 7•25 years ago
|
||
reassign this to ftang as M12
Comment 8•25 years ago
|
||
I have fix this bug for a while.
Reporter | ||
Updated•25 years ago
|
Status: RESOLVED → REOPENED
Reporter | ||
Updated•25 years ago
|
Resolution: FIXED → ---
Reporter | ||
Comment 9•25 years ago
|
||
I tested this in 01-05-16 Linux build. The caret does not move while typing Japanese characters before commit.
I need to reopen this.
Updated•25 years ago
|
Status: REOPENED → ASSIGNED
Summary: [PP][BETA] IME bug - Caret does not move while typing → IME bug - Caret does not move when type uncommitted text in over-the-spot IME style
Target Milestone: M12 → M20
Comment 10•25 years ago
|
||
ok, the problem is about caret movement in the pre composed text. I have no way
to fix it under over-the-spot input method style. However, this is a valid bug,
just low priority. Remove [PP] and [BETA] and move to M20
Updated•25 years ago
|
Assignee: ftang → tajima
Status: ASSIGNED → NEW
Target Milestone: M20 → M15
Comment 11•25 years ago
|
||
This should be solved by on-the-spot IME. Reassign to tajima@eng.sun.com
Assignee | ||
Comment 12•25 years ago
|
||
As frank said, pre composed window in over-the-spot style
is owned by XIM(like kinput2 on Linux), so that's XIM's
problem, but not mozilla. On the other hand, in on-the-spot,
mozilla draws pre composed text, so does caret. We plan to
check in a big patch for on-the-spot after M14. I'll mark
the bug resolved after the check-in, right?
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 13•25 years ago
|
||
The big patch has been checked-in.
(r=pavlov,ftang,erik, a=waterson)
Using on-the-spot inputstyle will show caret at the
current insertion point of text buffer.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 14•25 years ago
|
||
I verified this in 2000030209 Linux build.
Status: RESOLVED → VERIFIED
Updated•14 years ago
|
Keywords: inputmethod
You need to log in
before you can comment on or make changes to this bug.
Description
•