Issue in version >9 where if prop mode set to auto would be unable to change/edit the phone number input after the phone number has been formatted due to a bug in a compute value of parsedMode that leads to an endless changing of value of the phoneObject which would then change the parsedMode return value, which would then change the value of phoneObject, etc etc.
The main culprit of this seems to be of how an if condition is being handled making parsedMode return the inappropriate value when result?.format(toUpperCase(parsedMode.value)) is being executed.
Fix for #462 (and potentially #452)
Issue in version >9 where if prop
mode
set toauto
would be unable to change/edit the phone number input after the phone number has been formatted due to a bug in a compute value ofparsedMode
that leads to an endless changing of value of thephoneObject
which would then change theparsedMode
return value, which would then change the value ofphoneObject
, etc etc.The main culprit of this seems to be of how an
if
condition is being handled makingparsedMode
return the inappropriate value whenresult?.format(toUpperCase(parsedMode.value))
is being executed.