Decimal numbers with comma as placeholder fail validation in Chrome

If I put in the value "10,50" the browser chrome sends "10.5" in the post data and the validation in webform_number_format_match fails.

Whoa, I was not aware of that. HTML5 field elements are definitely still in the category of "very inconsistent" between browsers. Thanks for the report, I'll take a look at this when I get the chance. We've got several other issues with the number component as well, so it'll be good to fix these all before the next release.

I can't find any information on how to prevent Chrome from having this behavior. It seems to me that it's not possible to prevent it from doing this conversion. This unfortunately means that it's impossible for us to know the format that will be coming into the server. On Firefox, it'd be a comma (like you input originally), but on Chrome it'd be a decimal. This make validation very tough.

Potentially, we might avoid the use of the "number" HTML5 element until browser support is more consistent. The main reason we use it right now is to provide contextual keyboards for touch devices, but it seems there are alternatives for that, per http://danielfriesen.name/blog/2013/09/19/input-type-number-and-ios-nume...

Unfortunately I haven't been able to find a way to bring up a numeric keyboard that would allow commas and period characters as well. In iOS, you just get the integers when using the approaches described there.

So, at this point, not a lot of solutions. We'd need to give up iOS-friendly keyboards in order to solve this problem (which is probably worth it in my mind).

Fixed by virtue of fixing related issue #2290029: Thousands separator creates invalid value for HTML5 Number input by no longer using HTML5 form elements.

This fixes both 7.x-4.x and 8.x.