Open Bug 1200506 Opened 9 years ago Updated 2 years ago

ibus-mozc receives stale cursor coordinates when implicitly committing text w/o return key

Categories

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

All
Linux
defect

Tracking

()

UNCONFIRMED

People

(Reporter: yukawa, Unassigned)

Details

(Keywords: inputmethod, Whiteboard: tpi:+)

Attachments

(1 file)

- Environment
Linux (Ubuntu 14.04) with Firefox nightly 43.0a1 (2015-08-31) and ibus-mozc.
 - I can reproduce this issue with both ibus-mozc 1.13.1651.102 (from Canonical repository) and ibus-mozc 2.17.2111.102 (built from source available at https://github.com/google/mozc)

- Steps to reproduce
1. Go to http://textarea.org
2. Type 'きょうは'
3. Hit space key to convert 'きょうは' to '今日は'
4. Type 'いい'
5. Hit space key to convert 'いい' to 'いい'
6. Type 'てんき'
7. Hit space key to convert 'てんき' to '天気'
8. Type 'です。'
9. Hit enter key.

- Actual Result
After step 2, suggestion window is aligned to the bottom left of the composing text (good). However, the horizontal position of suggestion window will never change even after step 4-9.

- Expected Result
After step 3, suggestion window is aligned to the bottom left of the composing text '今日は'.
After step 5, suggestion window is aligned to the bottom left of the composing text 'いい'.
After step 7, suggestion window is aligned to the bottom left of the composing text '天気'.

- Note
The above issue does not occur if you explicitly commit text between step 3 and step 4, between step 5 and step 6.  See attached screen record for details.

This is probably an edge case that Bug 1120851 did not cover.  When I receive the original bug report https://github.com/google/mozc/issues/243 1 year ago, I thought this should be addressed ibus-mozc side like I finally did as https://github.com/google/mozc/commit/9fbcdd5e27cf26ff16d72bd2d92f269334912ede, but the truth was a bit more complicated.  It turns out that the original issue is rather specific to Firefox hence we cannot fix this in ibus-mozc side.  Sorry for not being able to report this issue earlier.  Seems that we need to change Firefox for this particular case.
Priority: -- → P4
Whiteboard: tpi:+
Component: Widget: Gtk → DOM: UI Events & Focus Handling
Keywords: inputmethod
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: