[w3c/payment-handler] PaymentRequestEvent.OpenWindow() could fail in two different ways (#361)

PaymentRequestEvent.OpenWindow(url) could fail in two different ways:
* reject - for example, "If url is about:blank, return a Promise rejected with a TypeError."
* resolve with null - for example, "If url's origin is not the same as the service worker's origin associated with the payment handler, return a Promise resolved with null."

What's the purpose of having two ways to refuse a failed "OpenWindow()". Can we merge them for developer ergonomics? 

(link to the Chrome Implementation discussion: crbug.com/1046120)

-- 
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/361