Closed Bug 1063568 Opened 10 years ago Closed 10 years ago

Data technology icon overlaps with signal

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:2.1+, b2g-v2.0 unaffected, b2g-v2.0M unaffected, b2g-v2.1 verified, b2g-v2.2 verified)

VERIFIED FIXED
2.1 S5 (26sep)
blocking-b2g 2.1+
Tracking Status
b2g-v2.0 --- unaffected
b2g-v2.0M --- unaffected
b2g-v2.1 --- verified
b2g-v2.2 --- verified

People

(Reporter: gerard-majax, Assigned: apastor)

References

Details

(Keywords: regression, Whiteboard: [caf priority: p2][systemsfe][CR 730038])

Attachments

(6 files, 1 obsolete file)

Attached image 2014-09-05-16-50-39.png (deleted) —
Reproduced on my Nexus S.
Assignee: nobody → apastor
Whiteboard: [systemsfe]
Target Milestone: --- → 2.1 S4 (12sep)
[Blocking Requested - why for this release]: It breaks the statusbar for non multi-sim devices
blocking-b2g: --- → 2.1?
blocking-b2g: 2.1? → 2.1+
Hi Alberto, just wanted to let you know that I'll test this when I get home today. I only have the flame on me atm.
Reproduced on: Alcatel One Touch Fire production (got from T-mobile Poland) B2G version: 2.2.0.0-prerelease master Platform version: 35.0a1 Build Identifier: 20140828040204 Git commit info: 2014-09-08 21:55:06 4acd3e69
Hi Alberto, I've added a spec to box: https://mozilla.box.com/s/5idustp1aqb9locwyqaz The main change is that the data is not left aligned with the signal icon. Also I've reduced the font size. let me know if you have any questions!
It seems I don't have access to that link :(
Flags: needinfo?(epang)
I think the proposed icon is too small, especially minding the screen quality of the devices that FxOS is aimed for. Perhaps, would be better to put a 'full-size' icon next to the signal as it was before?
Attached image [Spec 2.1] Single-Sim Connectivity (obsolete) (deleted) —
Albert, here is the spec. Eric, when you update for new specs, will you attach them to the bug instead of posting links to dropbox? We should be making these specs public.
Attached image [Spec 2.1] Single-Sim Connectivity (deleted) —
Hey Alberto, I've updated the spec to address the data connection being to small on lower resolutions devices - which we also noticed when testing yesterday. Let me know if you have any questions. Thanks! Sorry about that Michael, I'll start uploading specs to the bugs. The reason I've been using links is so that the latest spec is always seen. But I can do both :).
Attachment #8486878 - Attachment is obsolete: true
Flags: needinfo?(epang)
Then, are we assuming that 1 sim means low resolution? What should be the behaviour with a multi-sim device, but only one SIM inserted?
Flags: needinfo?(epang)
I'm jumping on Alberto's answer: I thought we were trying to avoid loosing too much space. With the proposed design, we have much more space wasted when connected on data network when roaming. Why don't we just have the same behavior than with multi-sim, and have a small letter indicating the network connectivity ? Because we can have also Dual SIM with small screen and Single SIM with good screen.
Talked offline to Eric, and the visual team is going to try to find a solution that works well in high/low resolution and still don't consume that many space. Will retake the bug after the specs are published here.
Flags: needinfo?(epang)
Attachment #8486049 - Flags: ui-review?(epang)
Comment on attachment 8486049 [details] Link to Github pull-request: https://github.com/mozilla-b2g/gaia/pull/23826 Hey Eric, could you please ui-review? Thanks!
Attachment #8486049 - Flags: ui-review?(epang)
Attached image 2014-09-12-01-28-21.jpg (deleted) —
Hey Alberto, Looks like we need a few fixes Dual Sim: - Reduce weight of data - maybe 1 or two weights down (let’s try 2 first) - Sim number need to be enlarged to match Data (same weight that we use above) and aligned to the bass of the signal icon Single Sim: - Reduce weight (which will be down above) - Data needs to be raised by 1 px since it’s currently touching the signal icon (I'm guessing if we do this for single sim that it will change for dual sim too? I'm hoping this looks ok on the flame)
Flags: needinfo?(apastor)
Hi Eric, Just updated the patch with: - font-weight reduced to 300 for both slot number and data type - Increased font-size of slot number to 10px - Data type raised 1px up (tested on a Keon and a Flame, and seems to be ok with the notifications bar) Hope I'm not missing something, but let's iterate over it on Monday.
Flags: needinfo?(apastor)
Comment on attachment 8486049 [details] Link to Github pull-request: https://github.com/mozilla-b2g/gaia/pull/23826 Looks good, thanks for troubleshooting an updating this! R+
Attachment #8486049 - Flags: ui-review?(epang) → ui-review+
Attachment #8486049 - Flags: review?(mhenretty)
Comment on attachment 8486049 [details] Link to Github pull-request: https://github.com/mozilla-b2g/gaia/pull/23826 CSS-only change, ui-reviewed. LGTM.
Attachment #8486049 - Flags: review?(mhenretty) → review+
Landing, because I want these changes on my dogfood phone. master: https://github.com/mozilla-b2g/gaia/commit/c21106017e7def8a436ec807a9fda746de5504ca
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Alberto, does this change depend on the roaming changes in bug 1056969? I think they do because the new data signal icon is in place of where the roaming icon used to be. If so, we will need to have those uplifted first. The sooner we do that the better, since those are polish bugs and this is blocking.
Flags: needinfo?(apastor)
Are you saying that you are experiencing this bug in 2.1? I thought none of the new data connections visual specs actually landed in 2.1. I'll try it tomorrow.
Flags: needinfo?(apastor)
(In reply to Alberto Pastor [:albertopq] from comment #22) > Are you saying that you are experiencing this bug in 2.1? I thought none of > the new data connections visual specs actually landed in 2.1. I'll try it > tomorrow. Hrmm, it looks like you requested this bug to block 2.1? If we are not experiencing this on 2.1, we can probably just remove the blocking flag.
Sorry about that. That wasn't meant to be asked for blocking. I'll double check tomorrow if it works properly in 2.1 before removing the flag, though. Thanks!
v2.1 is not affected by this. Unflagging. At the other hand, not sure if Bug 1056969 is in fact blocking making space to the rocketbar, so may be we need to uplift it (and all the dependents, including this one). What do you think?
blocking-b2g: 2.1+ → ---
Flags: needinfo?(mhenretty)
I think we should to be honest. Bug 1056969 solves a lot of spacial issues for the statusbar. Also, we still have a lot of polish work to do for 2.1 in the statusbar, and having master and 2.1 diverge can really complicate that issue.
Flags: needinfo?(mhenretty)
+1 How can we start that process?
I guess just start with request uplift on bug 1056969. Be as detailed as you can about why it's important to have it (ie. spacing issues and keeping complexity of fixing further statusbar bugs across branches). And make sure to mention this bug and bug 1066557 there in that request, so they know what this entails. We'll go from there.
Comment on attachment 8486049 [details] Link to Github pull-request: https://github.com/mozilla-b2g/gaia/pull/23826 [Approval Request Comment] [Bug caused by] (feature/regressing bug #): 1056969 [User impact] if declined: Data icon overlaps with the signal when only 1 sim [Testing completed]: Manual tests [Risk to taking this patch] (and alternatives if risky): Low risk, only CSS [String changes made]: -
Attachment #8486049 - Flags: approval-gaia-v2.1?
[Blocking Requested - why for this release]: Regression from 1056969, which has been uplifted
blocking-b2g: --- → 2.1?
Attachment #8486049 - Flags: approval-gaia-v2.1? → approval-gaia-v2.1+
blocking-b2g: 2.1? → 2.1+
Whiteboard: [systemsfe] → [systemsfe][CR 730038]
Whiteboard: [systemsfe][CR 730038] → [caf priority: p2][systemsfe][CR 730038]
This issue is verified fixed on Buri 2.1 and 2.2. Result: The data icon does not overlap with the signal icon on a single-SIM device. Device: Buri 2.1 BuildID: 20141118001204 Gaia: 1b231b87aad384842dfc79614b2a9ca68a4b4ff3 Gecko: 95fbd7635152 Version: 34.0 (2.1) Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Device: Buri 2.2 BuildID: 20141118040205 Gaia: 4aee256937afe9db2520752650685ba61ce6097d Gecko: 7913c9392c5f Version: 36.0a1 (2.2) Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
Status: RESOLVED → VERIFIED
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: