-
-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(web): prevent invalid longpress shortcut triggers #10641
Conversation
User Test ResultsTest specification and instructions Test Artifacts
|
@bharanidharanj It disappeared, rather than just moving to a different key? Could you record a video of some sort for what you're seeing? If it's not moving to a different key, I'm not getting the same behavior when I use the test artifact. |
@jahorton Yes . It disappeared, rather than moving to a different key. I have recorded a video file for reference. Here, the problem is If I move the mouse pointer (while long pressing the 'k' key) towards the label name 'k' in the key preview, then it (key preview) suddenly disappears from the keyboard. keypreview.mp4 |
TEST_SIMPLE_KEY_UP_FLICK: PASSED All I see is the 'k' key preview being replaced with an 'i' key preview - the key preview has "moved to a different key." Assuming the actual disappearance of the key preview at timestamp 0:15 was you releasing the held mouse-button / touch, I see no errors here. There's no stuck highlighting afterward, either. @bharanidharanj Would there be a better/clearer way to describe this intended behavior for any future user-tests to be written? It's pretty clear that you interpreted my original description of this behavior differently than I anticipated, so hopefully I can find something clearer for next time. |
Test Results
|
@keymanapp-test-bot retest TEST_RAPID_TYPING_STABILITY Your description of the test is from the other specified unit test, not the intended rapid-typing one. Easy enough mistake to make. |
I've gone ahead and recorded that result to its related issue. As previously noted, I was hoping that this PR might fix #10592 too, but that was only speculative... and it wasn't the original point of this PR anyway. |
Changes in this pull request will be available for download in Keyman version 17.0.266-alpha |
Fixes #10640.
When I put together #10172, I rightly considered how the changes would be affected for standard longpress timeouts... but wrongly forgot to apply the same sort of filtering whenever the longpress up-flick shortcut is executed.
By making the item-validator a full-on path-model property, rather than a path-model timer-only property, we can validate all finalizations, rather than only timer-based ones. The same filtering should apply for both cases, after all, so it makes sense as a configurable parameter on its new level.
User Testing
TEST_SIMPLE_KEY_UP_FLICK:
k
key.)There was a temporary extra test here at one point - see #10641 (comment) - which was used to gauge how related #10640 is to #10592 and whether or not the latter would also be fixed by this PR. Alas, this PR's changes are insufficient for the latter.