-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
cursor shifts away from textbox #426
Comments
Hi, could you record the behaviour so I can understand the pattern correctly? I've tried what you described on my Samsung tablet and the built-in SMS messenger but couldn't replicate it. |
I don't think the regular cursor movement should be able to move focus outside the textbox, especially since the cursor moves so fast. If you change the cursor movement behavior to move word by word you can no longer leave the textbox, but you also can't use it to check for extra spaces at the end since the cursor refuses to move there, this is also unexpected behavior. Tested on version 16.2 |
YouCut_20231120_105638589.mp4i just think the cursor should stay inside its textbox as default like in all other editors :) |
Problem here is because the code uses KEYCODE_DPAD_* (like in a controller, where it would be expected) instead of MOVE_CURRENT_END_POINT_* (what most keyboard behavior is like). Should be easy to change. @flide please fix |
I agree |
Cursor movements was moving the cursor out of the input box refs: 8VIM#426
@Redo11 A fix is available from #509. You can download the debug version from the private F-droid repo (https://github.com/8VIM/fdroid) P.S.: you can install those versions along the stable one they won't |
thanks |
) Cursor movements was moving the cursor out of the input box refs: #426
Using the 8vim cursor (by accident or to ensure a none space ending) sometimes gets me out of the textbox leading to unwanted behavior like eg sending sms.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The cursor should stay inside it's textbox.
Smartphone (please complete the following information):
Additional context
maybe this is considered not a bug but a feature. In this case there should be an on/off toggle for it.
The text was updated successfully, but these errors were encountered: