Re: [w3c/payment-handler] Default handler icon? (#178)

Thank you, @rsolomakhin, for writing this up following the 20 June payment apps call [1]. Here were the four take-away points (mostly covered by your post):

* We include a statement in the spec that says that app-level information is provided through other web technologies (e.g., web app manifest and fallback approaches).
* When there are no icons and labels available (for any of a number of reasons), we leave to the browser how to best manage a fallback user experience (e.g., using origin as you indicate; we also
mentioned favicons). 
* Browsers should not omit a matching payment handler from the list merely because of missing icons and labels.

Also +1 to the console warning.

Ian



[1] https://www.w3.org/2017/06/20-apps-minutes.html#item05

-- 
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/payment-handler/issues/178#issuecomment-309947884