Added to JIRA: https://issues.apache.org/jira/browse/TAP5-2409
On 29 Oct 2014, at 1:52 am, Barry Books <trs...@gmail.com> wrote: > There is a similar problem with type=date. The difference is wc3 does not > spec the date format so it could be anything. I solved it with a value > encoder. Unfortunately I don't think you can override existing ones > >> On Oct 28, 2014, at 8:01 AM, Geoff Callender >> <geoff.callender.jumpst...@gmail.com> wrote: >> >> I have a BigDecimal field 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. >> >> I haven't looked at what happens to group separators. They might cause even >> more trouble. >> >> Has anyone hit this same problem? >> >> Is there a workaround? >> >> Geoff >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
