- From: Matt Saxon <notifications@github.com>
- Date: Mon, 03 Apr 2017 04:03:11 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 3 April 2017 11:03:53 UTC
OK, sure... 2nd try. In section 7.4, it states that the algorithm replaces steps 6 & 7 in Payment Request. I think this statement is brittle and should say something like this replaces section X in Payment Request. I would recommend that the algorithm in [Payment Request in section 19.4](https://www.w3.org/TR/payment-request/#user-accepts-the-payment-request-algorithm) be updated to clearly show what is the responsibility of the "mediator" and what is the responsibility of the "payment app". I'd split this into 2 subsections myself, the one that pertains to Payment Apps can be referenced in the Payment Handler spec. This wouldn't specifically need a Payment Handlers spec as the browser could fulfil both roles in my mind. Currently is doesn't have these roles and is effectively written as a "form-filler". This is inappropriate for progression to CR status IMO. -- 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/browser-payment-api/issues/476#issuecomment-291112085
Received on Monday, 3 April 2017 11:03:53 UTC