Closed Bug 18398 Opened 21 years ago Closed 20 years ago

[dogfood][PP]IME bug-Shift+arrow key does not work correctly in unconverted string

Categories

(Core :: Internationalization, defect, P2)

x86
Other
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: teruko, Assigned: ftang)

References

Details

(Keywords: inputmethod, Whiteboard: [PDT+]12/6)

Before you convert the Japanese characters, you can use Shift+arrow key
to move inside the unconverted Japanese string.  However, Shift+left arrow
key does not move to the last character.

Steps of reproduce
1. Open the Composer
2. Change Character set to Japanese (Shift_JIS)
3. Turn on IME and select Zenkaku Hiragana mode
4. Type "にほんごてすと" (at this time, do not hit enter, yet)
    Characters are highlighted.
5. Use Shift + Left Arrow key 7 times

    Every characters should not be highlighted anymore, but only the first character "に" is
    still highlighted.

Tested 110909 Win32 build.
Status: NEW → ASSIGNED
Target Milestone: M12
Blocks: 16127
Priority: P3 → P2
Summary: [PP]IME bug-Shift+arrow key does not work correctly in unconverted string → [dogfood][PP]IME bug-Shift+arrow key does not work correctly in unconverted string
the key stock to type this Japanese is "korehatesuto"
The reproduce procedure is
1. turn Japanese IME
2. type 'korehatesuto'
3. hit space
4. shift + -> 3 times, it will select the whole 6 hiragana
5. now hit shift + <- 5 times, the first 2 times is right. the 3rd Shift+<-
should show the first 3 hiragana got selected. But instead, we got wrong IME
highlight.
Can you workaround this using the mouse?
If so, is it a Beta stopper but not a dog food bug?
No, there is no workaround.
Whiteboard: [PDT+]
Putting on the PDT+ radar.
Whiteboard: [PDT+] → [PDT+]12/6
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
The selection display code in nsTextFrame.cpp have problem in the while loop. I
just fix it and check it in. Now it should be fine.
Status: RESOLVED → VERIFIED
I verified this in 12-01-08 Win32 build under Winnt 4.0J and Windows 95J.
You need to log in before you can comment on or make changes to this bug.