Closed
Bug 1502223
Opened 7 years ago
Closed 7 years ago
Timeout Payment Request if updateWith/show promises take too long to resolve
Categories
(Core :: DOM: Web Payments, enhancement, P3)
Core
DOM: Web Payments
Tracking
()
RESOLVED
DUPLICATE
of bug 1498310
People
(Reporter: MattN, Unassigned)
References
()
Details
Similar to bug 1447773, if a merchant takes too long to respond to actions we should abort:
A) Slow to resolve a promise passed to .updateWith()
** Demo: https://rsolomakhin.github.io/pr/ko/promise/ is supposed to be a test page for the event promise case but it gives an InvalidStateError so it may be wrong.
B) Slow to resolve a promise passed to .show()
** Demo: https://rsolomakhin.github.io/pr/ko/timeout-show-promise/ for .show(promise)
The UI needs to be notified with `completeStatus: "timeout"` so we can show an error page.
Not sure if we should re-use dom.payments.response.timeout or have a new pref.
Side note: I think the current 5s value of dom.payments.response.timeout should be increased for low-bandwidth users and slow merchant backends. I regularly have transactions take over 5 seconds to process the payment.
Comment 1•7 years ago
|
||
I would like to fix this in bug 1498310.
Since these are related to the exception handling about no response from merchant while xxxchange event emitted.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Updated•7 years ago
|
Whiteboard: [webpayments-reserve]
You need to log in
before you can comment on or make changes to this bug.
Description
•