- From: Adrian Hope-Bailie <notifications@github.com>
- Date: Tue, 28 Feb 2017 04:12:08 -0800
- To: w3c/webpayments-payment-apps-api <webpayments-payment-apps-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/webpayments-payment-apps-api/issues/105/283023415@github.com>
So, having read the proposal in detail here are a few thoughts: **1. Wallets** I am still not convinced that the use case for wallets is strong enough to justify all the complexity it brings with it. Your first code example is so clean and easy to understand and doesn't require any new data models to carry icons, just a label and set of supported methods. I won't oppose to it being pushed through but my personal preference would be to hold off until we get feedback that it's required. **2. Multiple Service Workers per origin** None of your examples demonstrate what would happen if two Service Workers were registered from the same origin with no wallets. Would they be grouped together? I assume so. i.e. If I replace the scrip block from your first example with the following do I see the same thing? ```javascript function install_payment_app() { navigator.serviceWorker.register("visa.js") .then(function(registration) { registration.paymentAppManager.options.set( "4e05bb9d-fe26-415b-9cc3-ee2fc3877315", { name: "Visa Cash Rewards ending 3701", enabledMethods: ["basic-card"] } ); }); navigator.serviceWorker.register("amex.js") .then(function(registration) { registration.paymentAppManager.options.set( "41856018-7631-409e-b45b-45641465aa09", { name: "American Express ending 5006", enabledMethods: ["basic-card"] } ); }); navigator.serviceWorker.register("mastercard.js") .then(function(registration) { registration.paymentAppManager.options.set( "9f68610b-7515-4746-a3ec-a6c37fdc64f1", { name: "Master Card Business ending 9123", enabledMethods: ["basic-card"] } ); }); } ``` -- 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/105#issuecomment-283023415
Received on Tuesday, 28 February 2017 13:19:55 UTC