Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) from Matt N. on 2018-10-03 (public-webpayments-specs@w3.org from October 2018)

From: Matt N. <notifications@github.com>
Date: Wed, 03 Oct 2018 00:51:53 -0700
To: w3c/payment-request <payment-request@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/payment-request/issues/792/426543887@github.com>

The UA would only be guessing about what the issue was so wouldn't be able to communicate anything meaningful to the user. The merchant has context to provide the user so that's what they should do. I can't think of a valid reason for a merchant to not provide their own error… it's more likely a bug in their code and so an exception would be more useful IMO.

-- 
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/792#issuecomment-426543887

Received on Wednesday, 3 October 2018 07:52:15 UTC