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

Caret goes to the beginning in at least Firefox 25 when the input value is not empty. #262

Closed
agamemnus opened this issue Mar 24, 2014 · 7 comments

Comments

@agamemnus
Copy link

It should be at the end... At least Firefox 25 through 28, I believe.

You can see it in your calculator example.

There's also a problem with the cursor not being seen at all depending on where you are in the input box and what your CSS transform:scale value is, but that one might be a Firefox problem...

@Mottie
Copy link
Owner

Mottie commented Mar 24, 2014

Actually the caret should end up wherever you click inside of the input to open the keyboard.

Clicking between two numbers:

2014-03-24 06_44_48-virtual keyboard basic scientific calculator demo

The caret starts in that position:

2014-03-24 06_45_29-virtual keyboard basic scientific calculator demo

The calculator demo just has the numbers aligned to the right, so the majority of the time the user clicks in the empty space on the left, causing the caret to start at the beginning.

2014-03-24 06_43_13-virtual keyboard
2014-03-24 06_43_37-virtual keyboard

@agamemnus
Copy link
Author

  1. Type in 1234.
  2. Click outside the calculator to hide the keyboard.
  3. Click to the left of the first character in the input box. (I believe this makes the position undefined?)
    The cursor starts at 0 in Chrome. In Firefox, it starts at the end.

@Mottie
Copy link
Owner

Mottie commented Mar 29, 2014

Hi @agamemnus!

Hmm, I'm actually seeing the opposite of what you are describing. Chrome is moving the caret to the end when you click on the left, and Firefox places the caret on the left.

I'll investigate this further when I get a chance.

@Mottie Mottie added the Bug label Mar 29, 2014
@Kuzq
Copy link

Kuzq commented Apr 16, 2014

I had the same problem in FF. In my case, $.fn.caret from jquery_keyboard.js was conflicting with caret function from jquery_ maskedinput.js. So i just renamed it and this solved the problem.

@Mottie
Copy link
Owner

Mottie commented Apr 16, 2014

Hi @Kuzq!

Hmm, but I don't think the caret is being properly positioned, nor would it replace a selection properly... but if it does work, then that would solve issue #201.

@jaiminmoslake7020
Copy link

I have the same problem in google chrome ... issue #330 just see it..!!!

@Mottie
Copy link
Owner

Mottie commented Apr 9, 2015

This should be fixed in the master branch along with issue #343.

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

No branches or pull requests

4 participants