Re: [w3c/payment-request] Improve error codes (#871)

We've generally moved away from error codes like the above in the web platform... "Legacy code name and value" where there are now gaps: https://heycam.github.io/webidl/#idl-DOMException-error-names 

We generally don't want to distinguish too much between how browsers behave and exposing user actions.... like, the tab switching behavior where the payment sheet closes might be Chrome specific behavior, but not necessarily something another browser does (e.g., I might switch to my bank's site to check if I have enough money in my bank account before I make a purchase... on Firefox, I would expect the payment sheet to still be there and the site not to know that I'm doing something else).

Having said that, we could review the errors we are throwing and see if we can be more specific... distinguishing between developer error and user (agent) aborts would be good, but I would caution going beyond that. 


-- 
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/871#issuecomment-506625062