Re: [w3c/browser-payment-api] Consider revising the design of complete() (#122)

The existing design calls for three possible values here (success, failure and a third state representing "unknown"). That doesn't map well into the binary success/failure model that Promises provide, and the point of PR #163 was to expand from two choices into three.

While I agree that Promise would be a better choice if we could guarantee that the web page knows the success status, moving in this direction seems to reintroduce an already-solved problem. Perhaps we could include information in the resolution case to distinguish between "success" and "unknown"? It seems somewhat inelegant, but better than what we have now.

---
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/browser-payment-api/issues/122#issuecomment-216972964