Cancelling or choosing Not Now for installation of app does not stop spinning wheel



4 years ago
4 years ago


(Reporter: tericharles, Unassigned, Mentored)





(1 attachment)



4 years ago
Created attachment 8499717 [details]
Marketplace spinning wheel.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:32.0) Gecko/20100101 Firefox/32.0
Build ID: 20140923175406

Steps to reproduce:

Firefox: 32.0.3
Marketplace: Stage and Production

Summary: When either choosing 'Not now' or cancelling app installing, the spinning wheel of the Free button keeps going until page is refreshed.

1. Go to URL OR
2. Click the blue Free button on an app (spinning wheel displayed on button).
3. Choose 'Not Now' from the floating window.

Actual results:

Even though I chose 'Not Now', the Free button still has the spinning wheel. I kept watching to see if it would stop, but finally after several minutes, I refreshed my page which then stopped it. Note: seeing the same thing if I cancel out of the floating window (close this window 'X').

Expected results:

I would think that by either choosing 'Not Now' or cancelling that would stop the spinning wheel in the button, but the only way to stop it is to refresh the page.


4 years ago
Mentor: mbrandt

Comment 1

4 years ago
Is there an appropriate event that can be sent to the Marketplace when the user clicks "not now"?
Component: General → General
Product: Marketplace → Firefox
Version: 2014-Q3 → unspecified

Comment 2

4 years ago
(In reply to Andy McKay [:andym] from comment #1)
> Is there an appropriate event that can be sent to the Marketplace when the
> user clicks "not now"?

This like bug 675533, I think this is impossible.

And, I seen a popup "Sorry, you are currently offline. Please try again later." at bottom of the page and the "Free" button restored to its original appearance after click the "Free" button and then click the "Not Now" or do nothing about one minute.
Component: General → General
Product: Firefox → Marketplace
Version: unspecified → Avenir
Closing based on comment 2.  Sounds like a CANTFIX.
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.