W3C home > Mailing lists > Public > public-payments-wg@w3.org > September 2016

Re: [w3c/webpayments] propose to add encoding attribute to data set (#181)

From: ianbjacobs <notifications@github.com>
Date: Fri, 23 Sep 2016 04:32:14 -0700
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/181/249168661@github.com>
@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-249168661
Received on Friday, 23 September 2016 11:33:31 UTC

This archive was generated by hypermail 2.3.1 : Friday, 23 September 2016 11:33:33 UTC