[jira] [Updated] (TAP5-2409) type="number" fails when decimal separator isn't "."

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade updated TAP5-2409:
---------------------------------
    Attachment: 0001-TAP5-2409-add-a-test-for-validating-a-TextField-with.patch

I extended a test so it reproduces the issue. I haven't put much thought into how to fix this but I guess, we'll have to add special cases when a {{type}} parameter is specified for a {{TextField}}.

> type="number" fails when decimal separator isn't "."
> ----------------------------------------------------
>
>                 Key: TAP5-2409
>                 URL: https://issues.apache.org/jira/browse/TAP5-2409
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Geoff Callender
>         Attachments: 0001-TAP5-2409-add-a-test-for-validating-a-TextField-with.patch
>
>
> This probably affects versions before 5.4 too.
> I have BigDecimal fields that I'm editing with TextField. On mobile devices I would like a numeric keyboard to pop up, so I added type="number".
> This all worked just fine in English, but then I switched locale to French and found Tapestry's client-side validation rejecting it as not a number.
> Digging around, I found that with type="number", the W3C spec requires the browser to translate the field value to a String with a "." decimal separator. The problem for Tapestry is that Tapestry's validation always expects the field value to be untouched and in the format of the locale. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)