Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多
Open

Typing out text

blazer1048

For a few weeks now, trying to to type anything while using Firefox on android mobile is an exercise in frustration and insanity. It makes me want to tear my hair out. I type part of a word, and then it suddenly adds the autocompleted word after the end of the letter I already typed. It also keeps screwing up after apostrophes: I type "The car is Jo's car" for example, and suddenly the cursor makes a space after "Jo", but the cursor moves to behind the "s". The end result looks like "The car is Jo' car"s

I'm not making this up, it literally happened while typing the above line and I decided to leave it like that for you to see. Typing in firefox right now is maddening.

For a few weeks now, trying to to type anything while using Firefox on android mobile is an exercise in frustration and insanity. It makes me want to tear my hair out. I type part of a word, and then it suddenly adds the autocompleted word after the end of the letter I already typed. It also keeps screwing up after apostrophes: I type "The car is Jo's car" for example, and suddenly the cursor makes a space after "Jo", but the cursor moves to behind the "s". The end result looks like "The car is Jo' car"s I'm not making this up, it literally happened while typing the above line and I decided to leave it like that for you to see. Typing in firefox right now is maddening.

所有回覆 (3)

We're working on it. If you use Samsung keyboard, disabling some "smart typing" features in Samsung Keyboard settings might be workaround.

TyDraniu said

We're working on it. If you use Samsung keyboard, disabling some "smart typing" features in Samsung Keyboard settings might be workaround.

Any updates?

Also, and I get that this is askiaskingn a lot, but could you explain why this issue is even happening? It would at least sate my curiosity.

could you explain why this issue is even happening? It would at least sate my curiosity.

Android IME (InputConnection) often requests current editable text be synchronous. But Gecko has its on content process, so we have two data blocks for Java side (ShadowText) and content side (CurrentText). This is synchronous when Gecko notifies IME of text/selection changes.

After we introduced a bug, it doesn't notify Gecko of IME composing range during batch mode to avoid unnecessary selection changes. After ending batch mode, we will send current composing ranges. Without text changes, IME content observer doesn't notify widget of any changes. So calling onIMESynchronized causes unexpected text/selection changes. Then text transaction is broken.

由 TyDraniu 於 修改

問個問題

如果您還沒有帳號,您必須先登入帳號 來回覆文章。還沒有帳號的話,只能發問新問題