Closed Bug 984315 Opened 11 years ago Closed 11 years ago

Follow-up Bug 947189. Polish contact button content according to the length of operator, tel number and SIM indicator

Categories

(Firefox OS Graveyard :: Gaia::Contacts, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:1.4+, b2g-v1.4 fixed, b2g-v2.0 fixed)

RESOLVED FIXED
1.4 S4 (28mar)
blocking-b2g 1.4+
Tracking Status
b2g-v1.4 --- fixed
b2g-v2.0 --- fixed

People

(Reporter: jmcf, Assigned: mbudzynski)

Details

Attachments

(2 files, 1 obsolete file)

See attached screen with the issue described. Some UX input needed
Attached image 20140317_112808.jpg
issue captured
The issue is that if the operator name is too long or tel number itself the operator name /tel number and the SIM descriptor can overlap. This is a visual issue
blocking-b2g: --- → 1.4?
Flags: needinfo?(cawang)
ni? Jose on visual issue. Thanks!
Flags: needinfo?(cawang) → needinfo?(vittone)
Hi guys, please check out the DSDS visual specs for contacts, the carrier should be moved next to the phone type. Check it out: https://bug947186.bugzilla.mozilla.org/attachment.cgi?id=8374186 Best, Jose
Flags: needinfo?(vittone)
triage: 1.4+, the strings can be easily overlaping in DSDS devices
blocking-b2g: 1.4? → 1.4+
To fix this, you can do something like this: <button> <div style="display: flex"> <div style="flex: 1"> <span>012345</span> <span>, Jamon networks</span> </div> <div class="sim-indication">SIM 1</div> </div> </button> The extra wrapping div is because Gecko doesn't seem to support flex on buttons (I opened bug 984869). An alternative is to use a <div style="display: flex" role="button" tabindex="0">.
Michal, could you take a look at this please ?
Flags: needinfo?(mbudzynski)
Ok, I'm on it.
Flags: needinfo?(mbudzynski)
Assignee: nobody → mbudzynski
Attached file Patch (obsolete) —
Attachment #8393567 - Flags: review?(francisco.jordano)
Comment on attachment 8393567 [details] [review] Patch Removing the review flag until we have unit tests here, please ask for r? again when ready to go :) Thanks a lot!
Attachment #8393567 - Flags: review?(francisco.jordano)
Attachment #8393567 - Flags: review?(francisco.jordano)
Tests updated, patch ready to r.
Comment on attachment 8393567 [details] [review] Patch Almost there Michal! Left some comments in github: - Use mozL10n for appending the carrier value (specially the separator). - Unit test can be improved a bit, checking for the carrier value. - CSS rules, looking a bit weird to me, we are moving the phone number away from the phone icon. Thanks a lot!
Attachment #8393567 - Flags: review?(francisco.jordano) → review-
Attachment #8393567 - Flags: review-
Attached file Final Patch
Attachment #8393567 - Attachment is obsolete: true
Attachment #8394224 - Flags: review?(francisco.jordano)
Fixed, ready for r again!
Comment on attachment 8394224 [details] [review] Final Patch Nice, please merge once travis is green.
Attachment #8394224 - Flags: review?(francisco.jordano) → review+
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
v1.4: b09bf796d82ca7aa00d141a0cb705ee9cabfab47
Target Milestone: --- → 1.4 S4 (28mar)
One silly question: is there a missing space somewhere between number and carrier? Space is not in the string or the code either.
Flags: needinfo?(mbudzynski)
Francesco, Carrier name is now above the number, next to th phone type, so there is no space between them.
Flags: needinfo?(mbudzynski)
Thanks for the explanation.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: