The root cause of this behavior is not a Pega defect, but rather browser behavior exacerbated by an inconsistency with how browsers are interpreting the current HTML5 number input type standard.
In Chrome user is allowed to type 'E' and the + or - sign. All other characters are not allowed to even be typed in the field.In IE 11, user can type anything into a number input field. But upon tab out or blur the browser will wipe out the field if it is not a valid number.In Chrome it does not nullify the input field until one actually submits the form.So in both cases, the reason why user is able to submit the form is because the edit-validate rules were not even invoked, and also because there were no values to even validate.The browser itself wiped the values before Pega has a chance to perform any actions.
Please refer the following link for more information: https://collaborate.pega.com/question/number-presentation-format-accepts-character-ee
Posted: 2 years ago
Posted: 2 Dec 2019 3:58 EST
Ridwan Vinck (RidwanV9)