Currently with the autocorrect feature (I -> 1), if the user mistypes a post code, it will potentially be recognised as an entirely different postcode, eg
- User intends to type
TE57 9NG
- They mistype, and enter
TE57 ING - with I being below 9 on a qwerty keyboard
- UKPostcode parses this as
TE57 1NG
This means if its being used to validate the postcode, it will be accepted but as a different postcode than the one the user intended.
If UKPostcode is being used to normalise the postcode, than it will normalise the mistyped postcode to TE57 1NG - if the rest of the form is valid than the user will never realise that a different postcode to the one they were trying to enter (TE57 9NG) has been accepted by the system.
Can this auto-correct feature be made configurable so the developer can turn if off if if required?
Currently with the autocorrect feature (
I->1), if the user mistypes a post code, it will potentially be recognised as an entirely different postcode, egTE57 9NGTE57 ING- with I being below 9 on a qwerty keyboardTE57 1NGThis means if its being used to validate the postcode, it will be accepted but as a different postcode than the one the user intended.
If UKPostcode is being used to normalise the postcode, than it will normalise the mistyped postcode to
TE57 1NG- if the rest of the form is valid than the user will never realise that a different postcode to the one they were trying to enter (TE57 9NG) has been accepted by the system.Can this auto-correct feature be made configurable so the developer can turn if off if if required?