Skip to content
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 issues on ie with date separator #611

Closed
checkin247 opened this issue Oct 17, 2017 · 3 comments
Closed

cursor issues on ie with date separator #611

checkin247 opened this issue Oct 17, 2017 · 3 comments

Comments

@checkin247
Copy link

checkin247 commented Oct 17, 2017

Issue is related to IE,
Tested on IE and Chrome

I am using some logic to automatically add a separator on keyboard input for date separator.

Using the real keyboard there is no issue.
With mottie keyboard, the cursor moves back one position before the separator.
I also tried to add the separator with the typing extension....
I also tried kb.caret('end')

The only solution (after trying a lot) was using a jQuery plugin to move cursor to the end.

I implemented it with

$("input").on('focus', function(e){
	$(this).putCursorAtEnd();
});

Maybe this helps someone or there is a built in function to overcome this issue

@Mottie
Copy link
Owner

Mottie commented Oct 17, 2017

Hi @checkin247!

There is a built-in function to move the caret. It is as you mentioned kb.caret('end'). I think it isn't working because you need to update the last position – I'll update the internal function to do this automatically.

The problem is that this keyboard plugin isn't 100% compatible with masking plugins. They both will fight for caret control (see #201). Also mentioned in that issue is the problem with using mask plugins with screen readers and a possible solution.

@checkin247
Copy link
Author

@Mottie , thanks for taking the time to explain that to me.
I will try this out and comment

@Mottie
Copy link
Owner

Mottie commented Apr 19, 2018

I'm guessing this issue has been resolved, so I'm going to close it. If you continue to have problems, please feel free to continue the discussion in this thread.

@Mottie Mottie closed this as completed Apr 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants