- From: Adam Solove <notifications@github.com>
- Date: Fri, 26 Jan 2018 15:42:27 +0000 (UTC)
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 26 January 2018 15:42:49 UTC
While I understand the issue with edge-cases in E.164, I'm concerned about the spec being so broad that the resulting numbers become unusable. The example from @aestes above has a US number with special formatting (no big deal) but also no country code (big deal!). The form in which a phone number is presented to a user has meaning in the context of their system's locale settings and their own knowledge of what country their phone number is for. If that same user-facing value is passed as-is to a merchant, it may be misinterpreted. Can we at least require numbers to include country code? -- 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/payment-request/issues/652#issuecomment-360819511
Received on Friday, 26 January 2018 15:42:49 UTC