Closed
Bug 785329
Opened 13 years ago
Closed 13 years ago
The Back breadcrumb button doesn't work in app details page
Categories
(Marketplace Graveyard :: Consumer Pages, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
2012-08-30
People
(Reporter: cboldan.mozbugs, Assigned: potch)
References
Details
(Whiteboard: [janus])
Steps to reproduce:
1. Load Marketplace homepage https://marketplace-dev.allizom.org/
2. Click on an app that has reviews to load details page
3. Click the button to load the Reviews page.
4. Click the Back button from the header to load app details page.
5. Click the Back button again.
Expected results:
User is redirected to the previous page (listing page/homepage)
Actual results:
The button does nothing.
Notes/Issues:
Verified in FF17 (Win 7).
Screencast for this issue http://screencast.com/t/3PiD5kpj
Comment 1•13 years ago
|
||
Can you get better steps to reproduce for this, please? I'm confused.
Reporter | ||
Comment 2•13 years ago
|
||
1. Load the Reviews page for an app
2. Click the Back breadcrumb button twice (to get to the category listing page)
Looks like issue is no longer reproducing in https://marketplace-dev.allizom.org/ but I was able to reproduce it until yesterday. http://screencast.com/t/3ldMLjaq
Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Comment 4•13 years ago
|
||
This one's not a dupe.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 5•13 years ago
|
||
(In reply to Chris Van Wiemeersch [:cvan] from comment #4)
> This one's not a dupe.
I'm wrong. It was fixed this morning.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Comment 6•13 years ago
|
||
Assignee: nobody → thepotch
OS: Windows 7 → All
Hardware: x86_64 → All
Target Milestone: --- → 2012-08-30
Reporter | ||
Comment 7•13 years ago
|
||
Verified as fixed in https://marketplace-dev.allizom.org/ on FF18 (Win 7)
Postfix screencast http://screencast.com/t/EC4kGILRDw
Closing bug.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•