Replacing `setManifest`/`getManifest` with the `options` attribute seems like a good change, but I'm not so sure about the `wallets` attribute. While we have talked about the usefulness of being able to let a single origin contain multiple "Apps" that again can contain multiple "Options", I don't necessarily think that containing this entire hierarchy inside of a single Service Worker is a good idea. Will each of these "Wallets" typically be presented to the user as an "App"? Or will they again be grouped inside another "App" container? -- 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/pull/104#issuecomment-281330695
Received on Tuesday, 21 February 2017 12:25:08 UTC