Fields with Decimal data type require a zero before decimal point

Recently, we have upgraded from v5.13 to v6.4 and noticed that fields converted to a decimal data type require a zero before the decimal point. When the float data type was used (v5.13), we could enter .95 and it would format to 0.95. If I enter in .95 now, I will get the generic "Invalid number" message. Is this the expected behavior? And if so, why? If I have a user entering .95 which is a valid decimal and they receive a message saying it's invalid, then it will cause a poor user experience and unnecessary confusion. Thanks in advance.
1 answers

This was most likely not a conscious decision but a consequence of using a different library. If you really feel that it is impacting your users' experience you should definitely submit a ticket.