Closed
Bug 1077335
Opened 10 years ago
Closed 10 years ago
[Loop] Incorrect buttons order in confirmation screen for the Loop mobile application
Categories
(Firefox OS Graveyard :: Gaia::Loop, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: oteo, Assigned: arnau)
References
Details
(Whiteboard: [mobile app][not blocking][tef-triage])
Attachments
(1 file)
Checking the Loop application, we have detected that the buttons in the confirmation screens are not in the correct order as it's specified in the Building Blocks: http://buildingfirefoxos.com/building-blocks/confirm.html where Cancel button should be at the left and the action button in red at the right. Right now, we are seeing the incorrect order in confirmation screens for removing the entries in the call log, in the shared URLs tab, and when logging out from the Loop application but we should check all the confirmation screens used in the application.
Reporter | ||
Updated•10 years ago
|
Assignee: nobody → rnowmrch
Blocks: 1036490
Severity: normal → minor
Status: NEW → ASSIGNED
Whiteboard: [mobile app][not blocking][tef-triage]
Reporter | ||
Comment 1•10 years ago
|
||
Just adding that for logging out from Loop app, the right button for logging-out should be blue as it implies an action from the user
Assignee | ||
Comment 2•10 years ago
|
||
Attachment #8499537 -
Flags: review?(borja.bugzilla)
Comment 3•10 years ago
|
||
Comment on attachment 8499537 [details] [review] patch in github Please remove https://github.com/mozilla-b2g/firefoxos-loop-client/pull/151/files#diff-abb510c96091b0d61e7b3e62b4199de0R52, rebase and merge this! Thanks!
Attachment #8499537 -
Flags: review?(borja.bugzilla) → review+
Assignee | ||
Comment 4•10 years ago
|
||
Merged: 587a53f5ab1edf494e3a0b1c9f4e9bbd6e36554c
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 5•10 years ago
|
||
Verified on flame, Gecko-7107b06.Gaia-c1f6089, lopp version: dbe5bf3, Ram: 512M, and spanish and english languages.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•