Bottom row sometimes disappears while editing

[kvibber]

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.0.0

Affected Android/Custom ROM version

Android 14

Affected device model

Pixel 5

How did you install the app?

Google Play Store

Steps to reproduce the bug

Sometimes when typing and editing a multi-line piece of text, the bottom row (with the space bar) will just disappear from view. It still works - I can still press the empty area where the space bar and other keys would be, but the only way I've been able to get it to reappear is to close the keyboard and re-open it.

I've encountered the bug multiple times over the last few weeks, definitely in Google Messages and Tusky, possibly in K-9 Mail and Nextcloud Notes, but haven't been able to find a clear pattern.

Expected behavior

The entire keyboard should stay visible while it's in use.

Actual behavior

Sometimes the entire bottom row of the keyboard turns invisible, though the keys still respond.

Screenshots/Screen recordings

No response

Additional information

No response

[Aga-C]

It's a duplicate of #51.

[naveensingh]

@kvibber if possible, could you please provide a screenshot?

[kvibber]

Weirdly enough, it stopped happening after I filed the bug. I've been trying to trigger it to collect a screenshot, but haven't been able to.

It's not the same as the "sticky keys" bug where sometimes keys get stuck on the pressed animation. I get that too, and actually saw the stuck animation while typing this comment! (it cleared up when i switched to upper case and back). What I was seeing before was that the ?123 , 😀 . ⬅️ row would just disappear and leave an empty space -- sometimes -- until I'd hide the keyboard and re-open it again.

[kvibber]

I finally managed to get it to happen again, several times while writing this post in Tusky. I think it happened while switching letters to punctuation and back (which is why I left the last row unblurred), but again I couldn't get it to happen consistently.

In all cases, the invisible space bar and mode switch buttons continued to be functional, they just weren't visible at all.

Anyway, as you can see, this is at least a different symptom from #51, though I wouldn't be surprised if they have a common underlying cause.

[JesterDoobie]

I dont have a screenshot but just experienced exactly this issue a few moments ago, and again while typing this bug comment. I was ranting into a ColorNote note and pressed "?123" and my bottom row just disappeared visually, but I was still able to use buttons like space and comma if I just typed with muscle memory. Pressing back to close the KB didn't help me any, it would just pop back up again without a bottom row when I tspped text soace to summon it avain, I had to kill ColorNote from my recents and relaunch it to get it to come back.

Android 14 on a Oukitel C51, this app is V1.1.1 from Fdroid, ColorNote is V4.5.3 from the Play Store. The phone is 4 days old to me and "barebones stock," as they say, I'm still setting it up and adjusting to Android 14 (I know it's out of order in the naming scheme and all but so far I personally am calling Android 14 'Boston Creme,' a truly vile mass of sugar.)

Idk if I can reproduce the issue or not, I honestlt wasn't
Strikethru that last sentence, I JUST had it occur again while typing here now (12:13am pst, mon nov11'24) in FF and it was afaik the exact same sequence of events;
I'm typing away at some speed and hit ?123 to access #'s and symbols (and I always wait a split second to see the correct symbol popup) and my bottom row disappeared visually but was still there to use, no popup keys, though. I ALSO found a useful for me fix, however, I pressed ?123 again to flip pages to #'s again and my bottom row just reappeared. Maybe you have the bottom row 'anchored' seperately somehow and it's getting treated differently in the code somewhere when I press ?123 ?