Closed Bug 1129449 Opened 11 years ago Closed 11 years ago

If user cancels from provider page another click is required to send the status.

Categories

(Marketplace Graveyard :: Payments/Refunds, defect, P3)

Avenir
x86
macOS
defect

Tracking

(Not tracked)

VERIFIED FIXED
2015-02-10

People

(Reporter: muffinresearch, Assigned: muffinresearch)

References

Details

(Keywords: regression)

As provider redirected errors are now hitting the correct SPA page, error messages are displayed which then require the user to hit OK. For the USER_CANCELLED message we should instead render a throbber and do the cancellation immediately like we used to.
Assignee: nobody → scolville
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Priority: -- → P3
Target Milestone: --- → 2015-02-10
Here's some STR for this bug which should aid QA testing STR: * On stage start an app purchase with desktop FF. * Enter PIN * On the payment page (at the provider e.g. CC entry) click the cancel button * This will redirect back to mozpay What happens: * A screen appears with an OK button. The user needs to click OK to close the window and cancel the payment. What should happen * You should see a spinner with "Payment cancelled" and the window should close automatically. The above should also be the case for FFOS devices too except there's no popups involved.
Keywords: regression
The sinner with "Payment cancelled" is missing : http://screencast.com/t/ClpITlheP
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to Victor Carciu from comment #3) > The sinner with "Payment cancelled" is missing : > http://screencast.com/t/ClpITlheP If the spinner isn't seen but the payment is cancelled and you see the notification on the parent window. That's fine too. As long as you didn't have to click "OK" on an error page prior to cancellation.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
In this case everything is ok. Thank you.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.