You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Gabrielle Crawford (JIRA)" <de...@myfaces.apache.org> on 2010/02/23 19:56:28 UTC
[jira] Updated: (TRINIDAD-1683) client-side convertNumber causes
loss of precision
[ https://issues.apache.org/jira/browse/TRINIDAD-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabrielle Crawford updated TRINIDAD-1683:
-----------------------------------------
Resolution: Fixed
Fix Version/s: 1.2.14-core
Status: Resolved (was: Patch Available)
> 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
> Assignee: Gabrielle Crawford
> Priority: Minor
> Fix For: 1.2.14-core
>
> Attachments: maxPrecision_1.2.12.2.patch, maxPrecision_trunk.patch
>
>
> 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.