Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607)

marcoscaceres commented on this pull request.



> +              </li>
+              <li>Set the <a>country</a> attribute of <var>address</var> to the
+              end user's country as an upper case [[!ISO3166]] alpha-2 code or
+              to the empty string if none was provided.
+              </li>
+              <li>If <var>request</var>.<a>[[\options]]</a>.<a data-lt=
+              "PaymentOptions.requestPayerPhone">requestPayerPhone</a> is
+              false, set the <a>phone</a> attribute of <var>address</var> to
+              the empty string. Otherwise, set the <a>phone</a> attribute of
+              <var>address</var> to a user provided phone number, optionally
+              formatted to adhere to [[!E.164]], or to the empty string if none
+              was provided.
+              </li>
+              <li>Set the <a>languageCode</a> attribute of <var>address</var>
+              to a <a data-cite="!BCP47#section-4.5">canonicalized language
+              tag</a>, or to the empty sting if none was provided.

So, this opened this interesting can of worms: https://github.com/w3c/payment-request/issues/608 ... it might be simple to solve, but I need to look in detail at how Chrome implements this via the Unicode CLDR library. 

This area is new to me though, so will need to do a bit of research. 

-- 
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/pull/607#discussion_r137154002

Received on Wednesday, 6 September 2017 01:36:39 UTC