Re: [webpayments] Should we expose status change events in the browser API? (#41)

A snip from the TAG guidance on using promises:
https://www.w3.org/2001/tag/doc/promises-guide#legacy

> _Appendix: Legacy APIs for Asynchronicity_

> Many web platform APIs were written before the advent of promises, and thus came up with their own ad-hoc ways of signaling asynchronous operation completion or failure. These include:

(other examples removed for brevity)

>* XMLHttpRequest’s send method, which triggers onreadystatechange multiple times and updates properties of the object with status information which must be consulted in order to accurately detect success or failure of the ultimate state transition

>_If you find yourself doing something even remotely similar to these, stop, and instead use promises._


---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/41#issuecomment-183049419