Thanks so much for this input, Peter and I18n folks. Just noting for (a), you’ll be happy to hear that’s literally what we recommend in the spec: > It is RECOMMENDED that the language of the user interface match the language of the body element. I’ll write a full response for the other points, but the tl;dr is that at a glance we get most what’s mentioned for free from the IDL layer (DOMStrings are already UTF16, irrespective of payment dialog input fields). And we can defer to the merchant for script detection when they need it (hence removal of this attribute). If there is to be a script/lang detection mechanism, we should add that as native functionality to ECMAScript via the `Intl` API, rather than as a one off for this API. Then it would be globally useful, not just for addresses, but for any kind of input. -- 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/764#issuecomment-418899896
Received on Wednesday, 5 September 2018 22:18:47 UTC