It appears that igNumericEditor is limited to the "float" data type in javascript and because of this it can lose large numbers that a user may type in.
For example, if I create an igNumericEditor with maxValue of "99999999999999.99999" and then enter the value "99999999999999.99999" into the editor and tab out, it changes the value to "100000000000000.00000". This seems consistent with what the parseFloat() javascript function would do, but is there a way around this?
You can see the example I've attached. Just enter in the value "99999999999999.99999" in the editor and tab out.
Is there a way around this? how should larger numbers like this be handled?
Hello Ryan Rupp,
Thank you for posting on our forums. I will be happy to assist you with this issue.
I've investigated this issue regarding maxValue not being applied for larger numbers. To ensure that it will receive attention, I have logged this behavior in our internal tracking system with a Development ID of 171126. The next step will be for a developer to review my investigation and confirm my findings or to offer a fix, or other resolution.
I will be sure to update you on this post once a fix becomes available. Please let me know if you have any questions regarding this matter.
As per the investigation done by my Product Development team, this behavior is caused by a limitation of 64-bit floating point numbers. More information about this can be found on the w3schools website:http://www.w3schools.com/js/js_numbers.asp
To avoid this behavior, you may want to consider using RegEx validation.
Please let me know if you have any questions regarding this matter.