florisboard / florisboard

An open-source keyboard for Android which respects your privacy. Currently in early-beta.
https://florisboard.org
Apache License 2.0
5.79k stars 392 forks source link

Keyboard can get stuck with wrong enter-key icon #2097

Open Glitchy-Tozier opened 1 year ago

Glitchy-Tozier commented 1 year ago

Short description

I haven't yet figured out the specifics of this issue, but it seems like the keyboard actually doesn't properly adapt to the environment, but instead keeps the previously cached icon. See screenshots at end of Issue.

Steps to reproduce

  1. Navigate to Florisboard's Dev-settings and make Florisboard crash (This bug also happens without crashing the app, but I'm not sure how to consistently trigger it this way)
  2. Without opening Florisboard, navigate to any search panel in any app
  3. Click on it to start FlorisBoard. The enter-key should now contain a looking-glass
  4. Navigate to any app that incorporates multiline textfields (which should, in theory, decorate the enter-key with a newline-icon). Examples: Note-apps, Github comments, Signal
  5. Click on such a textfield to bring up Florisboard
  6. See bug: The looking-glass icon still is present

Environment information

Screenshot_20221026-115703_WhatsApp.jpg Screenshot_20221026-120030_WhatsApp.jpg Screenshot_20221026-120044_GitHub.jpg

patrickgold commented 1 year ago

This issue is not specific to the enter key I am afraid but to some sort of state bug, where FlorisBoard uses the nth-1 state instead of the nth state. I am saying this as this bug can also lead to the numeric keyboard getting stuck and being used for text fields, and in the last few weeks this has happened multiple times a week. This is definitely something which needs priority fixing, once I have published my first word prediction demo to the alpha track.

Glitchy-Tozier commented 1 year ago

Oohhh, getting the numeric keyboard to get stuck sounds fun! 🤩 (Though of course annoying if multiple issues arise from it)

klaurence commented 1 year ago

Regarding a possible state bug, could this be related with #2024? Since I've created that issue, I've also been experiencing a bug where the Select all button becomes inconsistently available when switching between using Termux and a regular app's textbox.