@mountielee and I discussed further. I believe the concern is about what happens in this situation: * payment request API is called in a context with character encoding A * the data is handed to a web-based payment app that uses character encoding B My assumption is that browsers manage this sort of translation from one encoding context to another. I would ask browser vendors to weigh in on whether they foresee any issues. Ian cc @ r12a -- 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/webpayments/issues/181#issuecomment-249168661Received on Friday, 23 September 2016 11:33:31 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:19 UTC