> Seriously, stop pushing for a manifest until its usage is defined. It feels like we're arguing about the tools before we decide what to build. I don't think that is the case. The proposal has always been to display a list of recommended apps to the user in the form of icons and labels. If you are suggesting the only safe way to present a list of recommended apps to the user is a list of URLs then I would propose we forget about the idea of recommended apps at all (or only show the user recommended apps they already have installed). My case for using a manifest IF we do want to display a list of icons and labels is that this seems safer than executing the service worker registration logic FIRST just so the script can provide these. Personally, I'd be happy for us to drop recommended apps entirely as I think it massively over-complicates the payment app spec, but I think I am in the minority on that. -- 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/48#issuecomment-274350435
Received on Sunday, 22 January 2017 18:53:17 UTC