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
selectionStart incompatible on latest Chrome #19
Comments
Hi Tom |
Yep, I’m seeing this as well — will prepare a fiddle and try and replicate it for you. |
Hey, managed to knock up a fiddle that replicates the issue exactly for me in at least the following chrome versions;
|
Thanks guys. As this is only happening in beta versions of Chrome, for now I'm going to assume this is actually a chrome bug. If you see it happening in any full release version of Chrome, please let me know and I'll definitely take another look. |
FWIW, I’ve had reports of this error from end-users who are also seeing this error on Chrome stable on mobile devices. |
Looks like Chrome has disabled the select api for inputs of type number and email. Apparently this is in line with the current whatwg html spec. This has affected several libraries as well as jquery.alphanum. I've sent the following email to the whatwg mailing list to try get clarification and to request that the select api be re-instated for input types email and password in the official html spec.
|
Awesome—thanks! |
FYI: Chrome stable on desktop is now exhibiting this behaviour. |
There's an active discussion currently happening on www.w3.org about possibly re-instating the selection API into the spec. This would fix the problem. It would be great if you could logon and add your support. |
I've also logged it as a bug in chromium so it would be great if you could also add your support there. |
Awesome — will do. Thanks. On 6 Mar 2014, at 2:25 am, KevinSheedy notifications@github.com wrote:
|
This issue seems to have also started occurring in the newly released Firefox 29. :( |
A little update on this issue. This also happens with type email. if you take @plasticine example and replace it with email. It will display the exact same error. Funny enough the input type tel works fine with the .numeric on top of it. Could anyone be kind enough to share a workaround for this error? |
Hi,
Chrome version: Version 33.0.1750.29 beta (and dev)
We're noticing errors when attaching to number fields:
Have you noticed this? Any known workaround?
The text was updated successfully, but these errors were encountered: