-
Notifications
You must be signed in to change notification settings - Fork 28
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 jumps to end of input field on up/down keys #45
Comments
I made a plunker... but can't reproduce the issue. Do anyone have an idea what might be causing this (when used in a large app)? |
Thanks for the plunker! Is there any other library interacting with |
Yes probably. This is the dependancy list (removed as many as I could).
Will also look into the directives we wrote ourselves, and see if any of them interact with |
I've increase the priority of the directive in v5.1.1. Try if it can fix your issue. |
I still have the issue. I just replaced datetime.js - did you change anything in custom-input? |
Nope. By increasing the priority, there is a chance to fix rendering issue (i.e. BTW, does it happen to the demo of custom-input too? |
I have the exact same issue. Additionally this happens when i just fill in parts of the date with numbers eg. i'm in the (day) section and type "1" followed by "1". After the second "1" is typed the cursor jumps to the end. |
Me too :( |
I found the problem is when jquery is in our page: https://plnkr.co/edit/KhYvapIHBxX0nHRpwjmX?p=preview |
The problem is that jQuery has different behavior with https://github.com/eight04/angular-datetime/blob/master/lib/directive.js#L67 |
Also, here is the plunker with it: |
Fixed in 5.1.2. |
I don't know if this is a bug or I'm missing something. But I can't get the arrow keys up/down to work properly. When I select the minutes (mm) and press key up it jumps to the end of the input field (after increasing the minute-value by one). The cursor doesnt jump in your demo, it stays and I can increase a value multiple times.
This is what I do:
The text was updated successfully, but these errors were encountered: