The problem is that the user agent might already have this information in its auto-complete database as free-form - or may get it from another application (e.g., Contacts.app on the Mac)... then it's kinda hard to normalize that data into E.164 or whatever because we won't have it in the correct format to start with. If anything, the UA SHOULD make an effort to return phone numbers in a standardized format... but developers cannot expect it ([robustness principle applies](https://en.wikipedia.org/wiki/Robustness_principle)) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/browser-payment-api/issues/390#issuecomment-271503389
Received on Tuesday, 10 January 2017 07:16:47 UTC