Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104)

@tommythorsen --
> In the screenshot above, have you given any thought to where the "Bank of America" string and the red Bank of America icon should come from?

The notion here is that the service worker has been registered from some context (i.e., an HTML page), and that context provides information specific to the web app. I'm hardly an expert here, but my understanding is that modern web browsers get the name from:

- The Web App Manifest indicated in the HTML via `<link rel="manifest" href="`*name of manifest file*`">`
- If that is not present, indicated in the HTML via `<meta name="application-name" content="`*app name*`">
- If neither is present, via `<title>`*app name*`</title>`

Similarly, the icon comes from:
- The Web App Manifest indicated in the HTML via `<link rel="manifest" href="`*name of manifest file*`">`
- If that is not present, indicated in the HTML via `<link rel="icon" href="`*icon location*`">
- If neither is present, from `/favicon.ico`

To be clear, I'm not proposing this *per se*; it is my understanding that this is how Web Apps in general are assigned names and icons for presenting to users. If we decide that this model isn't appropriate for payments, I don't *personally* have a problem with changing it -- but if we have an already-established pattern and set of tools for this kind of thing, we'll need some clear reasons for doing things another way.

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