Closed
Bug 1521458
Opened 6 years ago
Closed 5 years ago
NOTIFY_IME_OF_SELECTION_CHANGE may not handle mIMESelectionChanged well on non-e10s.
Categories
(Firefox for Android Graveyard :: Keyboards and IME, enhancement, P3)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: m_kato, Unassigned)
Details
GeckoEditableSupoort posts SetSelection widget event, but non-e10s mode may receive NOTIFY_IME_OF_SELECTION_CHANGE synchronously. So mIMESelectionChanged may be ignore on non-e10s. But e10s can handle this due to async.
NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED consider this situation, so I should consider NOTIFY_IME_OF_SELECTION_CHANGE handling too.
|
||
Comment 1•5 years ago
|
||
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
|
|
||
Updated•5 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•