genius.com - Unable to fully type when suggestions are still loading
Categories
(GeckoView :: IME, defect, P2)
Tracking
(Webcompat Priority:P2, Webcompat Score:6, firefox147 verified)
| Tracking | Status | |
|---|---|---|
| firefox147 | --- | verified |
People
(Reporter: rbucata, Unassigned)
References
()
Details
(Keywords: inputmethod, webcompat:platform-bug, webcompat:site-report, Whiteboard: [webcompat-source:web-bugs][webcompat:sightline])
User Story
platform:android impact:annoyance configuration:general affects:all branch:release diagnosis-team:dom user-impact-score:300
Attachments
(2 files)
Environment:
Operating system: Android
Firefox version: Firefox 110.0
Steps to reproduce:
- Navigate to: https://genius.com/
- Tap on the search bar
- Once prompted, type a sentence and observe
Expected Behavior:
Typing works correctly
Actual Behavior:
Typing shows issues if the suggestions are not loaded completely
Notes:
- Reproduces regardless of the status of ETP
- Reproduces in firefox-nightly, and firefox-release
- Does not reproduce in chrome
Created from https://github.com/webcompat/web-bugs/issues/119275
| Reporter | ||
Updated•1 year ago
|
| Reporter | ||
Updated•1 year ago
|
| Reporter | ||
Comment 1•1 year ago
|
||
Comment 2•1 year ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 3•1 year ago
|
||
I chased this all the way up to here https://searchfox.org/mozilla-central/rev/d4235354139ae0da3b15b89943b140b510a74f2f/widget/android/GeckoEditableSupport.h#149 and noticed we missed some ::OnNativeCall, so we missed some characters when typing. Then this seems to relate to how native events are dispatched on Android?
Masayuki, do you have ideas about this? I could ask the android folks to take a look if this is not something for DOM.
Android specific IME part is maintained by Makoto-san. Makoto-san, do you have any ideas?
Comment 5•1 year ago
|
||
As long as I looking video, text selection is updated incorrectly. But I cannot reproduce this... I have to find reproducing way.
Comment 6•1 year ago
|
||
Thanks for looking this Makoto-san.
I can reproduce this quite easily, just typing fast. For example, if I type helo, the last o often got eaten by something...Let me know if you want me to generate something for you.
For the purpose of triaging this, given I don't see evidences that the site does something wrong, so I'll label this as a platform bug for now.
I can reproduce this with either ATOK Pro or Gboard.
When I type text with ATOK Pro, the composition string was forcibly committed when (?) the throbber appears. Could be caused by focus handling?
Updated•1 year ago
|
Updated•11 months ago
|
Comment 8•7 months ago
|
||
Geckoview::IME seesm to be a good component for start.
Updated•4 months ago
|
Updated•3 months ago
|
Comment 9•3 months ago
•
|
||
This will be fixed by bug 1995911. Content has a lot of child documents, so GeckoEditable tries to reset keyboard from GeckoEditableSupport::TransferParent per finishing to create a child document.
Updated•3 months ago
|
Comment 11•3 months ago
|
||
REOPENING because we're generally keeping site issue bugs separate for each site and not duping them. I've added a dependency instead.
Updated•3 months ago
|
Comment 12•3 months ago
|
||
We can close it as fixed when the problem is confirmed fixed on nightly
Comment 13•2 months ago
•
|
||
After landing bug 1995911, composing text isn't committed during inputting a text. (Before that such as Firefox beta, when starting search, text is often committed)
| Reporter | ||
Comment 14•2 months ago
|
||
Verified as FIXED using RC Build fenix android-arm64-v8a
Tested with:
Browser / Version: Firefox 146.0 Build 2016129538
Operating System: Google Pixel 3 (Android 12) -1080 x 2160 pixels, 18:9 ratio (~443 ppi density)
Operating System: Oppo Find X5 (Android 13) - 1080 x 2400 pixels, 20:9 ratio (~402 ppi density)
| Reporter | ||
Updated•2 months ago
|
Comment 15•2 months ago
|
||
I'm a bit confused - bug 1995911 landed in 147 but this was verified as fixed in 146?
| Reporter | ||
Comment 16•2 months ago
|
||
This bug had no milestone set, so when we are doing a re-verification with the RC Build, if it has the current version fixed (146 in our case) we are acting accordingly.
Comment 17•2 months ago
|
||
Right, but my point is that if bug 1995911 is what was expected to fix this, 146 should still reproduce. Working correctly on 146 isn't the expected result.
| Reporter | ||
Comment 18•2 months ago
|
||
Correct, I can still see a delay in 146 RC Build. I've missed that, sorry about the confusion
| Reporter | ||
Updated•2 months ago
|
| Reporter | ||
Comment 19•2 months ago
|
||
I've re-edited the report and added the 147 milestone. Please feel free to modify as you see fit, if it is not correct.
Comment 20•2 months ago
|
||
Sounds like the bug should be reopened then unless it's been verified on a Nightly 147 build...
Updated•2 months ago
|
| Reporter | ||
Comment 22•1 month ago
|
||
The latest Beta for Firefox Android works as expected, version 147b2. When typing, the caret does not jump, and words are typed correctly while suggestions are loading
| Reporter | ||
Comment 23•1 month ago
|
||
Updated•1 month ago
|
Comment 24•1 month ago
|
||
Verified, the issue no longer reproduces.
Tested with:
- Browser / Version: Fenix 147.0-candidate build 1
- Operating System: Google Pixel 5 (Android 14)
Updated•1 month ago
|
Description
•