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

I propose to recommend a web app manifest or its `<link>` equivalent fallback. If no labels or icons are found after all of the fallbacks, a browser can degrade the experience gracefully.

For example, an unlabeled payment handler can be sorted to the bottom of the list of payment apps and be identified only by its origin:

1. [Label] [Origin] [Icon]
1. [Label] [Origin]
1. [Origin] [Icon]
1. [Origin]

It would be prudent for the unlabeled payment handler to print a developer console warning, "No label/icon found for payment handler. Experience is degraded."

-- 
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-309778321