client-side convertNumber causes loss of precision
--------------------------------------------------
Key: TRINIDAD-1683
URL: https://issues.apache.org/jira/browse/TRINIDAD-1683
Project: MyFaces Trinidad
Issue Type: Bug
Components: Components
Affects Versions: 1.2.12-core
Reporter: Cale Scholl
Priority: Minor
ISSUE:
----------
JS numbers are 64-bit values and thus only have 16 digits of precision; this
isn't enough to represent the max value of a Long, BigInteger, or BigDecimal.
This means that when we convert a number string to object then back to string
on the client, we can lose precision, even though we wouldn't lose any
precision on the server.
FIX:
-----
Only render a client converter if the input value is bound to a supported type
(Float, Double, Integer, Short, Byte). The JavaScript number is a 64-bit
floating type and has enough precision to represent any of these supported
types.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
