Open Bug 1249568 Opened 9 years ago Updated 2 years ago

[TSF] candidate window is bottom of window when input composition (2 or more characters) on Code Mirror using Google Japanese IME

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P3)

Product:
Core
Component:
DOM: UI Events & Focus Handling
Platform:
Unspecified
Windows 10
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox47 --- affected

People

(Reporter: m_kato, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: inputmethod, Whiteboard: tpi:+)

- Env Windows 10 + Google Japanese IME - Step 1. https://codemirror.net/ or scratchpad 2. Turn on IME 3. Input 'あ' 4. Input 'あ' again - Result When step 3, candidate window is located under composition string. But step 4, it is located under window instead.
Codemirror uses textarea (width is 3px?) to input composition string. I think, when inputting 2 characters, second character isn't visible area. So GetTextExt returns (0,0,0,0)...
Keywords: inputmethod
Summary: [TSF] candidate window is bottom of window when input composition (2 or more characters) using Google Japanese IME → [TSF] candidate window is bottom of window when input composition (2 or more characters) on CodeMirrror using Google Japanese IME
Summary: [TSF] candidate window is bottom of window when input composition (2 or more characters) on CodeMirrror using Google Japanese IME → [TSF] candidate window is bottom of window when input composition (2 or more characters) on Code Mirror using Google Japanese IME
Priority: -- → P3
Whiteboard: tpi:+
I wonder, if we could detect if focused editor were too small for using it directly, we could return first character's rect instead? (I think that even if its size is 0-0, we should treat the size as 1em x 1em at least. I guess that width should be larger than 1em at least and height should be larger than 1em for normal usage. And the visibility property value is also useful.

Moving all open keyboard/IME handling bugs to DOM: UI Events & Focus Handling component.

Component: Widget: Win32 → DOM: UI Events & Focus Handling
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.