So recently one of my apps has had some problems on Chrome.
The app has an input field that is using the HTML5 type=numberEnter
I have a jQuery script in place, that takes care of validation, in case the user enters a comma to separate decimals from the initial integer (most users are Danish, and in Denmark, ',' is used instead of '.'). Previously the script would look at the value of the input field on form submit, but as of the latest version of chrome, this script yields "" (empty string) when called on a field containing a number separated from its decimals by a comma:
$('#input_field_using_number').val(); // = "", should be = "2,5" (example)
I'm parsing novalidate="novalidate" to the form, as chrome will freak out if commas are used in number fields, and I don't want to get in my users face about it, and would rather just fix it for them, before posting the data. Chrome is now breaking this (all other browsers are fine).
What should I do? Any workaround, or am I in the hands of Google, or have to force my users to use the dot, although they are used to using the comma?
Thank you,
/Andreas