Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650)

> I spoke with our implementation team about this, and although receptive to the idea, this wouldn't be high priority for Mozilla to implement. We are planing to do a staged rollout of localized payment sheets over the next year(s), so we could eventually support this... but it would take time.

To clarify, we have a similar problem to what @rsolomakhin mentions… that we currently only ship one language pack per build by default. Then we'll have to deal with reading from multiple at a time. Currently our fallbacks for untranslated strings are done at build time, not runtime.

> Having a single language through the payment flow has, in our experience, increased conversion.

Was this experience with using a native payment UI that's not embedded in the webpage? I think the value of this will come down to whether users think of the Payment Request UI as part of the webpage or as part of the browser. There are some cases where users may want their UA language to be used, not the page language, for example, if I'm not fluent in the supported languages of the merchant site, having the PR UI in my preferred language will be easier for me to use/understand.

-- 
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/650#issuecomment-345401302