A few days ago, you reviewed the #BB-806 issue, I understand your concern regarding the backend submission failure, but after testing the changes locally, I found that when using parseFloat, the value remains as a float (e.g., 5.5), which provides proper visual feedback to the user if they enter a float.

However, when using parseInt, a value like 5.5 gets converted to 5, which leads to an error on submission because the input is no longer a valid float.

To address this, I switched to using parseFloat to preserve the float value and ensure that the validation is both correct visually (i.e., informing the user about incorrect input) and on submission.

I'll share a screenshot to show the result.

Thanks for your input!