Closed
Bug 1029175
Opened 10 years ago
Closed 10 years ago
[Homescreen] Notification tray needs visual attention
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(b2g-v2.0 fixed, b2g-v2.1 fixed)
RESOLVED
FIXED
2.0 S6 (18july)
People
(Reporter: pla, Assigned: nefzaoui)
References
Details
(Whiteboard: ux-tracking, visual design, visual-tracking, bokken [ucid:SystemPlatform60, 2.0, ft:system-platform])
Attachments
(3 files, 1 obsolete file)
(deleted),
image/png
|
Details | |
(deleted),
text/x-github-pull-request
|
alive
:
review+
bajaj
:
approval-gaia-v2.0+
|
Details |
(deleted),
image/png
|
pla
:
ui-review+
|
Details |
Currently, the notifications tray looks very confusing when you pull it down. The transparency coupled with the segmentation caused by each notification's background rectangle makes the tray not 'read' as a single panel. I propose a couple of small, low-effort tweaks that can vastly improve the experience of pulling down and using the notifications tray. Please see attached spec for details. This bug can be considered a sister bug to this one: https://bugzilla.mozilla.org/show_bug.cgi?id=1022429 as they both work to align the notifications tray more with the visual refresh. However, I would consider this one more important from a UX standpoint.
Assignee | ||
Comment 1•10 years ago
|
||
Assigning myself, would love to work on it!
Assignee: nobody → nefzaoui.ahmed
Assignee | ||
Comment 2•10 years ago
|
||
Hey Alive, could you review this for me please? Thanks
Attachment #8444830 -
Flags: review?(alive)
Assignee | ||
Comment 3•10 years ago
|
||
And the screenshot for UI review.
Attachment #8444836 -
Flags: ui-review?(pla)
Updated•10 years ago
|
Attachment #8444830 -
Flags: review?(alive) → review+
Comment on attachment 8444836 [details]
Screenshot - After Patch
Hi Ahmed,
Thanks for taking on another one! :) Everything looks great, except the baseline for the date is now one pixel too low when compared to the time. If you can fix this, I'll give it a ui-review+.
Attachment #8444836 -
Flags: ui-review?(pla) → ui-review-
Assignee | ||
Comment 5•10 years ago
|
||
It seems like another bug took care of the status bar date (seems like the font update just did it). So I rebased, took off the status bar edit, and here's a new screenshot.
Attachment #8444836 -
Attachment is obsolete: true
Attachment #8451201 -
Flags: ui-review?(pla)
Comment on attachment 8451201 [details]
Screenshot 2 - After Patch
Looks great! Thank you!
Attachment #8451201 -
Flags: ui-review?(pla) → ui-review+
Ahmed, can you attach a link to the patch? Alive, can you approval-b2g review+ it for 2.0? This fix is pretty low risk, high reward. Thanks!
Flags: needinfo?(nefzaoui.ahmed)
Flags: needinfo?(alive)
Assignee | ||
Comment 8•10 years ago
|
||
Sure,
We have attachment 8444830 [details] as a patch.
Flags: needinfo?(nefzaoui.ahmed)
Comment 10•10 years ago
|
||
Comment on attachment 8444830 [details] Github pull-request 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 changes made]: See comment 7, asked by visual.
Attachment #8444830 -
Flags: approval-gaia-v2.0?
Comment 11•10 years ago
|
||
Comment on attachment 8444830 [details]
Github pull-request
low risk, css changes..
Attachment #8444830 -
Flags: approval-gaia-v2.0? → approval-gaia-v2.0+
Assignee | ||
Updated•10 years ago
|
Keywords: checkin-needed
Comment 12•10 years ago
|
||
Master: https://github.com/mozilla-b2g/gaia/commit/f445a1ac660d5ad4d710f2e88b4f693a9752c8f6
Status: NEW → RESOLVED
Closed: 10 years ago
status-b2g-v2.1:
--- → fixed
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → 2.0 S6 (18july)
Comment 13•10 years ago
|
||
v2.0: https://github.com/mozilla-b2g/gaia/commit/a867ab091d8f01b9c68f420ca97e880e06e25871
status-b2g-v2.0:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•