Closed Bug 827804 Opened 12 years ago Closed 12 years ago

[Lockscreen UX] Entering passcode. "Emergency call" and "Cancel" buttons should be vertically centered

Categories

(Firefox OS Graveyard :: Gaia::System::Lockscreen, defect)

x86
macOS
defect
Not set
normal

Tracking

(b2g18+ fixed)

VERIFIED FIXED
Tracking Status
b2g18 + fixed

People

(Reporter: vicky, Assigned: pivanov)

Details

(Whiteboard: visual design, UX P3, uxbranch, landed in uxbranch, yedo)

Attachments

(3 files)

Both texts should be vertically aligned in the middle and be 6,5 pt. See attachment.
Whiteboard: visual design, UX P3
Assignee: nobody → pivanov
Attached image After patch (deleted) —
Attached file patch for UX branch (deleted) —
Attachment #710854 - Flags: review?(sjochimek)
Comment on attachment 710854 [details] patch for UX branch Pavel, seems that we lost the white color in the two buttons (https://bug827804.bugzilla.mozilla.org/attachment.cgi?id=710852) also i don't understand why you use a :after for a vertical alignment ?
Attachment #710854 - Flags: review?(sjochimek) → review-
Whiteboard: visual design, UX P3 → visual design, UX P3, uxbranch
I update the PR(fixed the white color) :after - it was used for easy vertical centering of text, regardless of its size(multi line text)
Whiteboard: visual design, UX P3, uxbranch → visual design, UX P3, uxbranch, landed in uxbranch
Attachment #710854 - Flags: review- → review+
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: visual design, UX P3, uxbranch, landed in uxbranch → visual design, UX P3, uxbranch, landed in uxbranch, yedo
Comment on attachment 710854 [details] patch for UX branch Hi Pavel, Checking in on this (per Jaime's email) as we strive to wrap up all Yedo and VxD changes by April 5th. Is this ready to raise to approval? with user value and risk in the comments? Let me know. Thanks!
Yes, this one is ready :)
Comment on attachment 710854 [details] patch for UX branch NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings. [Approval Request Comment] Bug caused by (feature/regressing bug #): User impact if declined: Testing completed: Risk to taking this patch (and alternatives if risky): String or UUID changes made by this patch:
Attachment #710854 - Flags: approval-gaia-v1?
Master commit hash is 2d65422
Can someone please fill out the form in comment 9, esp with regards to risk.
Comment on attachment 710854 [details] patch for UX branch Please renominate with a risk evaluation.
Attachment #710854 - Flags: approval-gaia-v1? → approval-gaia-v1-
Pavel, can you fill in the information in comment 9 please?
Flags: needinfo?(pivanov)
Also to note, I can't verify this because of bug 855107.
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #14) > Also to note, I can't verify this because of bug 855107. This is fixed in Bug 847552 can you check it again?
Flags: needinfo?(pivanov)
verified the alignment, the problem is with l10n items: bug 858754. Also filed bug 858716
Comment on attachment 710854 [details] patch for UX branch NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings. [Approval Request Comment] Bug caused by (feature/regressing bug #): Incorrect vertical alignment of button text User impact if declined: Bad experience Testing completed: Tested in the device (Unagi) Risk to taking this patch (and alternatives if risky): Low risk (it only includes classes in the HTML code and CSS updates) String or UUID changes made by this patch: None
Attachment #710854 - Flags: approval-gaia-v1- → approval-gaia-v1?
Comment on attachment 710854 [details] patch for UX branch approving for uplift since bug 858754 does not, to our knowledge, look to affect shipping locales for v1.1
Attachment #710854 - Flags: approval-gaia-v1? → approval-gaia-v1+
I was not able to uplift this bug to v1-train. If this bug has dependencies which are not marked in this bug, please comment on this bug. If this bug depends on patches that aren't approved for v1-train, we need to re-evaluate the approval. Otherwise, if this is just a merge conflict, you might be able to resolve it with: git checkout v1-train git cherry-pick -x -m1 25d9e53380db967d76223c5f1e1940ed907ed447 <RESOLVE MERGE CONFLICTS> git commit
Sam/Pavel, can you please looks into this? Thanks :)
Flags: needinfo?(sjochimek)
Sorry wrong hash, uplifted from 2d654221796a99d2b6e02d56605a553fe053f965 v1-train: 7c55debc55174791399a182cca216cd1d038d538
Flags: needinfo?(sjochimek)
Verified w/ Unagi on v1-train Gaia: 0ddb515f15cbc6b74fc2742b7599d6ae74c6413f Gecko: 5d2cf5184ac6f99758668da9e6a5b1a34f9fefc8
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: