material-ui-phone-number
material-ui-phone-number copied to clipboard
alexplumb
conflicts with autocomplete and different number formats
If I let Chrome autocomplete the form that contains this component, which a lot of people do, this breaks. My saved form data doesn't have the country code in it (most people here in the US don't use it). I live in Los Angeles, so my normal 10-digit number starts with 310. material-ui-phone-number assumes that "31" is the country code, and that i live in the Netherlands. I'm hoping that I just missed something that deals with this, but so far I don't see anything.
Same issue here, after looking through the docs and trying the different flags on the component there doesn't seem to be anything built in that addresses this issue.
To me it seems like if I have countryCodeEditable={false} then the autocomplete from Google shouldn't overwrite the country code but it does.
For now I have just disabled autocomplete on this field in order to prevent a more frustrating user experience with autocomplete overwriting the user's selection but it would be great to see support for the countryCodeEditable={false} to prevent autocomplete from changing the country code.
+1 for this. Our app serves demographics who are international, too. Browser autocomplete breaks it.
I have the same issue with autocomplete on MacOS (Safari). Mac try to past the +33 666600000 phone number, but instead of recognizing the +33 aera code, the +66 Area code is set to Thaïland code (+66). When I'm trying to autocomplete on Chrome, the aera code is field with 06 and the dialog says that the country code is incorrect.
When I set the default Aera code +33 in my app, if the phone number is starting with +, it should replace the country code correctly. If the area code is not starting with +, it should keep the default country code.
As someone as a solution for that?
