feat(web): enhanced flick resetting via path base-coord replacement 🐵

[jahorton]

Rather than requiring a user to remember exactly where their initial touch location was for a flick during resets, this set of changes allow for flicks to 'change' their start location when reset. A location nearish the center of the base key will always be chosen in a manner that also favors the actual location of the active contact-point when reasonable.

Deliberately not picking the actual center, but an off-center location with a moderate radius of it toward the actual location of a touch, it becomes far easier to swap flick direction intuitively after a reset.

User Testing

TEST_FLICK_LOCKING: Using the standard "Test unminified KeymanWeb" test page from a mobile device...

1. Select "English...", then "Gesture Prototyping".
2. Tap and hold the u key.
3. For the following steps, pay attention to the animated preview.
4. Drag it purely north (straight up) - you should see the û key in the preview area (assuming it's not blocked by your finger).
   • If the animation was "jumpy" - if there was a lack of motion at the same time you moved your finger, then a big "jump" to catch up - FAIL this test.
   • If any such "jumps" were directly tied to you moving your finger quickly, do not fail this test.
5. Return your finger to the original 'u' key; the 'u' key should slide back into place.
   • Note when the preview's u fully recenters: that indicates a successful "reset".
6. Now drag your finger downward: you should see a preview for ü as you do so.
7. Return your finger to the original 'u' key; the 'u' key should slide back into place.
8. Now, drag your finger in a up-and-right motion: you should also see a preview for ú as you do so.
   • Again, if the animation felt "jumpy" and not well connected to your input, FAIL this test.
9. While the ú is visible and in the center, lift your finger and end the gesture.
10. Verify that a ú is output.
11. Repeat steps 2 through 6 for the a key; you should see similar previews and text there. (â, ä, á)

NOTE: this should replace the corresponding test from Web's regression-test specification if possible. Consider it an update.

[keymanapp-test-bot]

User Test Results

Test specification and instructions

• ✅ TEST_FLICK_LOCKING (PASSED): ):** Tested using the standard "Test unminified KeymanWeb" test page from a mobile device (Samsung Galaxy- Android version 13) and here is my observation: 1. Selected "English - Gesture Prototying" keyboard. 2. Tap and hold the 'u' key. 3. Dragged it to straight up position to see û letter. Did not see any 'jumpy' animation. 4. Returned the finger to its original position. ('u' key) 5. Dragged it to downword side and I was able to see ü key. 6. Again, return to 'u' key. 7. Then, dragged it to up-and-right motion to see ú letter. Lift my finger and ended the gesture. Verified that a ú letter appears on the text screen. 7. Repeat the steps for the 'a' key and I was able to see the similar previews and texts there. (notes)

[bharanidharanj]

Test Results

• TEST_FLICK_LOCKING (PASSED ): Tested using the standard "Test unminified KeymanWeb" test page from a mobile device (Samsung Galaxy- Android version 13) and here is my observation: 1. Selected "English - Gesture Prototying" keyboard. 2. Tap and hold the 'u' key. 3. Dragged it to straight up position to see û letter. Did not see any 'jumpy' animation. 4. Returned the finger to its original position. ('u' key) 5. Dragged it to downword side and I was able to see ü key. 6. Again, return to 'u' key. 7. Then, dragged it to up-and-right motion to see ú letter. Lift my finger and ended the gesture. Verified that a ú letter appears on the text screen. 7. Repeat the steps for the 'a' key and I was able to see the similar previews and texts there.