Tl;dr: @adamroach, indicating in the affirmative. Please close this issue. @adrianhopebailie, wrote: > On the topic of "manifest duplication", I personally attempted, on more than one occasion, to engage the editors of the app manifest specification to provide input into this work or review our use case. Specifically I wanted to find ways to re-use parts of app-manifest without duplicating it but those attempts, to put it politely, didn't end well, so let's leave that there. I'm really sorry that we the Editors let you down - but the reality is that what you were asking for didn't make any sense to us, which is why we were doing so much head scratching when you reached out to us. We were all like, "...but... we already provide all that stuff, why do you want it again?". Anyway, just trust the page to include: `<link rel=icon> OR `<link rel=manifest>` OR even a favicon OR `<meta name="application-name">`. If it doesn't, that's also ok! It's just a crap app and the browser can provide a fallback icon. -- 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/98#issuecomment-274988292
Received on Wednesday, 25 January 2017 00:58:11 UTC