Re: [w3c/payment-handler] What happens when clearing site data? (#236)

@annevk wrote: 
> I'd like to strongly object to declaring UX problems out-of-scope. That just leaves your mess for someone else to clean up. It's imperative that you consider workable end-to-end solutions.

Agree. We definitely want to be thinking about how this data could be represented - and how it can integrate with existing browser utilities. We've done a lot of mockups along the way too.  

Don't read this whole bug, but just for example (UI/UX mockups of browser integration):

 * Permissions dropdown: https://github.com/w3c/payment-handler/issues/98#issuecomment-274743326 and https://github.com/w3c/payment-handler/issues/98#issuecomment-274745455 
 * Browser UI: https://github.com/w3c/payment-handler/issues/98#issuecomment-275021705
 * More browser UI, how developers might use it, and "Browser Settings":  https://github.com/w3c/payment-handler/issues/98#issuecomment-275581133

We've done that throughout the process. 

@adrianhopebailie wrote:
> Can spec the CRUD interface as being via SW and leave it at that?

We certainly could, but that makes the API unnecessarily difficult to use. I would still like to be able to use `PaymentInstrument` store to create parts of the UI in the web application.  Conveniently, it's what I wanted to show here ("wallet.com" graphic): https://github.com/w3c/payment-handler/issues/98#issuecomment-275581133 

If the `PaymentInstrument` was only in the service worker, then the developer would have to do painful message-passing/data-cloning to show what's in the `PaymentInstrument` to the user in a nice way (better than static icons). 


-- 
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/236#issuecomment-349906807