[Browser] Overflow Menu Refinements

RESOLVED INVALID

Status

Firefox OS
Gaia::System::Browser Chrome
RESOLVED INVALID
4 years ago
4 years ago

People

(Reporter: epang, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [systemsfe])

User Story

VisD: https://mozilla.box.com/s/urudcnxj6ub4ov95ltx7
(Reporter)

Description

4 years ago
A few visual refinements are needed.

1. The overflow icon should stay blue when active and appear on top of the overlay.
2. Check that strings and icons are all vertically centered in their sections.
3. Is font weight reg?  It looks a little thick, can we try going one weight lighter?
(Reporter)

Comment 1

4 years ago
Hi Chris,

I just have a few more items to add :).

1.  Will the blurry icons be fixed?  I remember you saying that you had a bug for them already (so ignore this if it's the case)
2. Can we try vertically centering the menu (it's not what's in the spec, but would be less of a reach for the user)
3. Update the underlay to #a6a6a6 (it's a little light now in my spec).

I'll update the spec soon, sorry for the updates!
Assignee: nobody → chrislord.net
Flags: needinfo?(chrislord.net)
Blocks: 1054466
No longer blocks: 945259
It seems we are tracking the visual spec changes for context menu in bug 1054466. Moving to block rocketbar-next if we don't have stuff to do this release.
Blocks: 1054414
No longer blocks: 1054466

Comment 3

4 years ago
Is this something we want in 2.2? (the nicer-looking overflow menus) If so, just flagging it for design - The SMS app needs to be looked at (bug 1054283).
Flags: needinfo?(chrislord.net) → needinfo?(pdolanjski)
(In reply to Chris Lord [:cwiiis] from comment #3)
> Is this something we want in 2.2? (the nicer-looking overflow menus) If so,
> just flagging it for design - The SMS app needs to be looked at (bug
> 1054283).

Likely.  I'll mark as 2.2? for now.
blocking-b2g: --- → 2.2?
Flags: needinfo?(pdolanjski)

Comment 5

4 years ago
Unassigning for now, I expect this will end up being part of the larger work of making all apps use wilsonpage's new shared web components.
Assignee: chrislord.net → nobody
blocking-b2g: 2.2? → ---
feature-b2g: --- → 2.2?
Is this story still in 2.2 scope?
Flags: needinfo?(pdolanjski)

Comment 7

4 years ago
It isn't, as it would require multiple other places to change to the newer visual design (which has, unfortunately, been descoped for 2.2).
feature-b2g: 2.2? → ---
Flags: needinfo?(pdolanjski)

Comment 8

4 years ago
I don't think this is worth having open actually, given that it was refinements to a partial implementation that has since disappeared (and will be replaced by wilsonpage's new webcomponents when we get round to implementing it again). Closing this as invalid now, feel free to reopen if you think I've made a mistake.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.