Upward swipes sometimes don't register

[Nixill]

Steps to reproduce

1. Use a layout that has up-swipes from the top row, such as programmer
2. Set the swipe length to a number like 70
3. Swipe upwards on a top-row key such as r, starting your swipe somewhere near the top of the key
4. Swipe up-left on a top-row key such as r, again starting your swipe somewhere near the top of the key

Expected behavior

The upward (3) and up-left (4) gestures should be input, such as ^ or "

Actual behavior

The tap (3) or left (4) gestures are input, such as r or <.

version of the program

3.2.1

Android version

Android 13

Device

Google Pixel 6a

Other details

Phone is rooted and using LineageOS 20-20231104-NIGHTLY-bluejay (I should really update that...)

It feels to me like the phone is treating the swipe as never going higher than the top of the keyboard. Notably, a swipe upwards from the bottom of the key will work, same as a swipe upwards from the bottom of the h key will still produce a q even if you don't swipe into the r key, but it is noticeably harder to get an up-swipe from the top row than from another row.

Acknowledgements

• I have written a short but informative title.
• I have updated the app to the latest version.
• I have searched the existing issues and this is a new one, NOT a duplicate or related to another open issue.
• This is not a question or a discussion, in which case I should have gone to lemmy.ml/c/thumbkey
• This is a single bug report, in case of multiple bugs I will open a separate issue for each one (they can always link to each other if related)
• I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements. 🤡
• I have filled out all of the requested information in this form.

[glm4610]

This is something I mentioned in another issue, which happens because of how Android clamps the pointer motion data to within the IME window. Because of that, we can't properly track user gestures which wander upwards. I think Unexpected Keyboard has a good workaround for this. I'll take a look at it this week

[breversa]

I’m having a similar issue with the FR v2 layout:

In the top-left square, the top-right symbol (the french apostrophe "'") rarely registers properly : it’s the right symbol ("^") that is input, unless I very precisely swipe in a not-totally-but-almost vertical way (= in the 1 o’clock direction from the center of the square).

As far as I know, it doesn’t happen with other squares/positions.

Thumb-Key 3.2.6
Fairphone 5
/e/OS 2.1 = Android 13

[Noitarud]

rightward guestures on right keys (redo, cut and whatever … is) and upward guestures on top (settings) do not work.

perhaps abstractly related: noted the rightward stroke ")" is difficult to enter, only possible if I swipe from left side instead of centre.

To fix rightward, move a little from edge(#783). Topward doesn't matter for me(move from (invisible) top?!) but adds confusion, place on bksp or fixed down-right #

[pxeemo]

If I'm not mistaken this is because gestures are not registered out of the keyboard area which works fine in Android 14+ based on my experiments
Also scrolling emojis upwards out of the keyboard's area doesn't work in Android 13 which was fine in Android 14+

[mpsijm]

You're correct in saying that the positions of the gestured are clipped to be within the keyboard area, I also experimented with this a while ago.

Unfortunately, on my Android 14 phone (Samsung Galaxy A33, latest update as of today), this is not yet fixed... Scrolling in the emoji list still stops when my finger moves outside the keyboard's area.