- From: Domenic Denicola <notifications@github.com>
- Date: Tue, 23 Jan 2018 20:12:46 -0800
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 24 January 2018 04:13:30 UTC
domenic commented on this pull request. > @@ -3354,22 +3351,6 @@ <h2> consent. </p> </section> - <section> - <h2> - Exposing available payment methods - </h2> - <p> - Developers might try to call the payment request API repeatedly with Personally I find consolidating privacy considerations into a single section to be a good idea. The difference would be that you'd have a pointer to the parts of the algorithms that help preserve privacy, instead of adding MAY stuff there. So I would change this to include all the same helpful overview of the problem, then point to the mitigations we've put in place in show() and canMakePayment(). -- 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/673#pullrequestreview-91060947
Received on Wednesday, 24 January 2018 04:13:30 UTC