Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809)

@mnoorenberghe wrote:

> That is also bad because it causes dataloss for anything the user had typed into the Payment Request dialog that wasn't saved into persistent storage. 

Potentially, yes. But it's Handler dependent and there are a few guards in place: consider, a web page can't arbitrarily cause another sheet to be closed down without the user explicitly clicking on another pay button. 

Also, there is no reason that the payment sheet that is being shut down couldn't keep the data in the sheet in a temporary state (and restore the state if the user hits pay again... so its mostly a UX problem, I feel). 

Thus, I think we should leave it to handlers to deal with it (e.g., Apple Pay deals with it in it's own way, for valid reasons). Firefox will deal with it differently for "basic-card". And so on...  

@adrianhopebailie wrote: 

>  I would suggest we don't make this a CR-Exit issue as it is adding complexity that we haven't really explored and could be bigger than we think... Examples:... 

These are great questions, but I think we need to address them as part of Payment Handler.  

The problem is that we have a spec requirement that implementations are not following and/or willfully violating - so we won't be able to move out of CR unless we address this somehow. 


-- 
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-request/issues/809#issuecomment-440120004