Closed
Bug 876388
Opened 12 years ago
Closed 12 years ago
"Successfully signed in" message displayed after submitting an app
Categories
(Marketplace Graveyard :: Developer Pages, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
2013-06-20
People
(Reporter: julian.mozbugs, Assigned: basta)
References
Details
(Keywords: regression)
Steps to reproduce:
1. Load Submit An App page https://marketplace-dev.allizom.org/developers/submit/
2. Complete all the fields and submit an app
3. Finish the app submission and get to step 4 (Finished! page)
Expected results:
There are no design or layout issues.
Actual results:
"Successfully signed in. Click here to reload." message is displayed under the footer.
Notes/Issues:
Verified on FF24 (Win 7).
Screencast for this issue http://screencast.com/t/NYchvA7K
Comment 1•12 years ago
|
||
*cvan talks about how basta knows how to fix this bug*
Wil: So basically you're throwing basta under the bus?
Cvan: I'm not throwing him under the bus. I'm saying he's very competent in this area
Assignee: nobody → mattbasta
Priority: -- → P2
Comment 3•12 years ago
|
||
This is still reproducible, but only on stage.
| Assignee | ||
Comment 4•12 years ago
|
||
No, it's still reproducible everywhere; it just has a much more complicated set of steps to reproduce. It's not an edge case, but it'll happen on subsequent (i.e.: not the first) logins after a certain period of time has passed.
The fix here is to ignore navigator.id.watch when we know the user is logged in already and pay attention to it when they're not.
| Assignee | ||
Comment 5•12 years ago
|
||
This should fix it:
https://github.com/mozilla/zamboni/commit/e7eb8854183a4ff675de598febc51c79063e2952
Reopen if the problem is still reproducible.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2013-06-20
| Reporter | ||
Comment 6•12 years ago
|
||
Verified as fixed in https://marketplace-dev.allizom.org/developers/ on FF24 (Win 7).
Postfix screencast http://screencast.com/t/hwLSaiOg6osd
Closing bug.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•