Agreed with @marcoscaceres, but the question is, what real error can we use? Preferably not one that is private-browsing-mode specific. `NotSupportedError` is used for the case where there are no payment methods available, so it seems like a reasonable candidate. Are there any other candidates that show() might reject with in the normal course of operation? In terms of spec change, if we go with NotSupportedError we could say this is an implementation detail and that in private browsing mode implementations may just decide that no payment methods are available. That this is allowed could probably be a bit clearer in the spec though, e.g. by inserting a step like > Optionally, reject acceptPromise with a "NotSupportedError" DOMException and abort these steps. > > NOTE: this allows the user agent to decide, without consulting any payment apps, that the payment request cannot be fulfilled. For example, in certain privacy-sensitive modes user agents may take advantage of this step. -- 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/448#issuecomment-284522747
Received on Monday, 6 March 2017 20:32:17 UTC