Closed Bug 1651257 Opened 4 years ago Closed 4 years ago

Duplicated input with Xiaomi keyboard

Categories

(GeckoView :: IME, defect, P2)

Unspecified
All

Tracking

(firefox80 fixed)

RESOLVED FIXED
mozilla80
Tracking Status
firefox80 --- fixed

People

(Reporter: ekager, Assigned: m_kato)

Details

Attachments

(1 file)

Originally reported: https://github.com/mozilla-mobile/fenix/issues/12282

Steps to reproduce

Input Chinese anywhere in the browser include URL bar with Chinese Pinyin input.
demo

Expected behavior

Correct input.

Actual behavior

More letters before.

Device information

  • Android device: Xiaomi Redmi Note 8 Pro
  • Fenix version: Nightly 200704 06:01
    Android Version: 10
    SoC: MediaTek Helio G90T(ARM64)

In the environment I encountered, every time a Chinese character was successfully created by the Pinyin input method, the English that made it up would be redundant before.

This does not happen sometimes, but it happens often.

There is no such problem in other software such as Google Chrome, Twitter, Youtube and Fennec


Similar to https://bugzilla.mozilla.org/show_bug.cgi?id=1639071 , https://bugzilla.mozilla.org/show_bug.cgi?id=1470786 and https://bugzilla.mozilla.org/show_bug.cgi?id=1569007

Flags: needinfo?(m_kato)

I look this.

Assignee: nobody → m_kato
Flags: needinfo?(m_kato)

Waiting report's reply since I cannot reproduce on GBoard. So I don't know reproduce environment. (Xiomi's keyboard only?)

Summary: Duplicated input with Chinese Pinyin → Duplicated input with Xiaomi keyboard
Severity: -- → S3
Priority: -- → P2

This is interesting that I cannot reproduce this using Google Playstore version (https://play.google.com/store/apps/details?id=com.iflytek.inputmethod.googleplay) since it doesn't use inline editing. I cannot find a setting for it.

https://treeherder.mozilla.org/#/jobs?repo=try&revision=01c0f0814b755ce674be8cf1330a8a793d53f5d6

This is timing issue when using iFLYTEC keyboard in Xiaomi App Store.

Although replace text transaction often dispatch dummy text change, it may be
unnecessary when other text change is already in text change queue. This issue
occurs if dummy text change is dispatched in the queue and other text change
is also dispatched in the queue.

AddIMETextChange merges old text change with newer text change when its range
is overlapped, but it doesn't consider range is same. So if same range, we
should adjust old end simply.

GV-junit test case emulates this situation, but since this is timing issue,
we won't reproduce this by this test case. But it is useful to check future
regressions.

Pushed by m_kato@ga2.so-net.ne.jp:
https://hg.mozilla.org/integration/autoland/rev/5442e71d1612
iFLYTEC IME often commits composition string unfortunately. r=geckoview-reviewers,snorp
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla80

Moving some keyboard bugs to the new GeckoView::IME component.

Component: General → IME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: