@ianbjacobs > Wouldn't that be taken into account the next time I visit the site? (There may be a separate issue about how caching is managed for this information, but that seems out of scope for our spec.) Well, each page within the site can have different icons and names. It would be feasible to update this information every time the user visits the exact same web page from which they originally registered the service worker. *However*, how likely is it that they will ever visit that exact page again? The service worker was probably registered from some kind of a "signup" page. Why would the user go there again? @adrianhopebailie > Isn't this up to browsers to define? Do we need to specify anything as relates to UI? The Service Worker life cycle is already well-defined. I think this is up to us to define. We have introduced the payment options with corresponding names and icons, and it's up to us to define their entire life cycle. It would be nice if we could inherit this behavior from the Web App Manifest specification, but [that particular section](https://w3c.github.io/manifest/#updating) is not very helpful. In light of this, it doesn't seem unreasonable to postpone thinking about updating this information until after v1 of our specification, though. -- 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-284687432
Received on Tuesday, 7 March 2017 10:49:21 UTC