Closed
Bug 1125165
Opened 10 years ago
Closed 10 years ago
There is no clear delimitation between terms links in payment confirmation page
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P5)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
2015-01-27
People
(Reporter: madalin.cotetiu, Assigned: dani)
References
()
Details
Steps to reproduce:
1. Open marketplace homepage.
2. Find a paid app and complete the payment flow until the payment confirmation page.
Expected results:
There are no layout or display issues in the payment confirmation page.
Actual results:
The 2 links displayed in the payment confirmation page have no clear delimitation, the user can be confused about which link he clicks.
Notes/Issues:
Verified in FF38(Win7) in marketplace.allizom.org
Screencast for this issue: http://screencast.com/t/G5DdS0L45on
Comment 1•10 years ago
|
||
How does it compare on device? Is it not the same problem?
Flags: needinfo?(madalin.cotetiu)
Reporter | ||
Comment 2•10 years ago
|
||
It looks the same on FFOS 2.0 (Flame). I wasn't aware of an existing bug about this issue.
Flags: needinfo?(madalin.cotetiu)
Comment 3•10 years ago
|
||
It's always been there, removing Desktop blocker.
Assignee: nobody → santi
No longer blocks: 969539
Updated•10 years ago
|
Priority: -- → P3
Updated•10 years ago
|
Priority: P3 → P5
Assignee | ||
Comment 4•10 years ago
|
||
The bug has been fixed
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Comment 5•10 years ago
|
||
(In reply to Daniel Oliver from comment #4)
> The bug has been fixed
Resolution: WORKSFORME → FIXED
Reporter | ||
Comment 6•10 years ago
|
||
This looks good on desktop and on Android but on FFOS 2.0 & FFOS 2.1 (Flame) there still is no delimitation between the links. (Not reproducing in FFOS 1.4 inari device)
Please view this screenshot (flame with FFOS 2.0): http://screencast.com/t/R2sgcqVKcAc
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 7•10 years ago
|
||
I have tested on Flame with FFOS 1.3 and it looks good to me. Maybe the browser cache wasn't cleared when it was re-tested? Please confirm after cleaning cache and cookies.
Screencast capture: http://www.screencast.com/t/H1y2QUjx
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•