Closed Bug 204491 Opened 23 years ago Closed 23 years ago

IME: cursor position is at the beginning of the string with un-commit mode

Categories

(Core :: Internationalization, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED WONTFIX

People

(Reporter: amyy, Assigned: ftang)

Details

(Keywords: intl)

Build: 05-01 trunk build on WinXP-JA Steps to reproduce: 1. Launch browser and go to any text area that can input Japanese characters, e.g. Composer window, text fields inside web page, URL location bar ...etc. 2. Start input, but not commit yet, e.g. type "nihonn" with hiragana mode. 3. Press space key to bring up the candidate window. Actual Result: The mouse cursor focus is at the beginning of the string. Expected Result: The mouse cursor should be at the end of the string. MS Notepad and IE do like that.
Frank, should that be reassigned to you?
This is only Windows problem.
adt: nsbeta1-
Keywords: nsbeta1nsbeta1-
Clearing nsbeta1- for reconsideration. This is a very bad usability problem. Works in Netscape 7.02.
Assignee: smontagu → ftang
Keywords: nsbeta1-nsbeta1, regression
Restoring nsbeta-. Clearing "regression" from keywords. Frank looked into this with Yuying. My earlier comment: > This is a very bad usability problem. Works in Netscape 7.02. is wrong on both counts. This is not a regression. The cursor position returns to the correct position after committing the IME text. The cursor position while in candidate mode is different from notepad and OE, but it is not clear which is correct. I marked this WONTFIX, but it could also be argued as INVALID...
Status: NEW → RESOLVED
Closed: 23 years ago
Keywords: nsbeta1, regressionnsbeta1-
Resolution: --- → WONTFIX
Mark this one as won't fix. But this problem is not invalid, the IME correct behavior should not put the cousor position at the beginning before commit. You can check this on every where, not only the MS IE or Notepad, but also on Ichitaro JA-IME, Mac JA-IME, linux JA IME ..., the cousor always at the end of the un-commit string.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.