In light of recent discussions including on 7 February [1], I propose that we: * Remove recommended payment apps from the payment app API. * Continue to work on recommended payment apps in the payment app task force, either looking for good practice (e.g., the merchant can react to a rejection of the promise returned from show()) or some other approach to recommendations outside of the communication between browser and payment app (for example, through some declarative means outside the API; I think AdrianHB mentioned he could explore the use of HTTP Link headers). This will let us move the spec forward and continue to discuss a recommendation "layer" independently (as Marcos also suggests [2]). Ian [1] https://www.w3.org/2017/02/07-apps-minutes#item03 [2] https://github.com/w3c/webpayments-payment-apps-api/issues/48#issuecomment-278294679 -- 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-payment-apps-api/issues/74#issuecomment-278340715
Received on Wednesday, 8 February 2017 14:20:32 UTC