Closed
Bug 971460
Opened 11 years ago
Closed 11 years ago
[Camera][Madai] 1.4 Visual Design Camera Settings Menu
Categories
(Firefox OS Graveyard :: Gaia::Camera, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: amylee, Assigned: wilsonpage)
References
Details
(Whiteboard: ux-tracking, visual design, jian [fxos:media] [m+])
Attachments
(3 files, 3 obsolete files)
Visual design for camera settings menu
Will attach visual specs
Reporter | ||
Updated•11 years ago
|
blocking-b2g: --- → madai?
Summary: [Camera][M] 1.4 Visual Design Camera Settings Menu → [Camera][Madai] 1.4 Visual Design Camera Settings Menu
Assignee | ||
Updated•11 years ago
|
QA Contact: wilsonpage
Reporter | ||
Comment 1•11 years ago
|
||
CSS pixel measurement specs for Settings menu
Updated•11 years ago
|
Assignee: nobody → wilsonpage
Reporter | ||
Comment 2•11 years ago
|
||
Updated spec for secondary menu items/confirmation message
Comment 3•11 years ago
|
||
Ashish!
Please attach the screenshot of current implementation to be reviewed by Mozilla UX.
And request Amy to review.
Reporter | ||
Comment 4•11 years ago
|
||
Here is the spec for the settings menu while in 1:1 and 4:3 aspect ratios. The rule is that in any orientation, the settings menu button always stays in the same position. Let me know if you have any questions.
Reporter | ||
Comment 5•11 years ago
|
||
Hi,
Here is a revised settings menu spec. The settings menu is now full screen to be more flexible in different situations/aspect ratios.
Attachment #8377354 -
Attachment is obsolete: true
Attachment #8384183 -
Attachment is obsolete: true
Comment 6•11 years ago
|
||
Comment 7•11 years ago
|
||
Dear Amy and Rob,
If settings menu spec is revised, we need to revise UI scenario for closing setting menu.
Please refer the attachment 8384930 [details].
But I don't agree to change it. Because user can only close it when user click the setting menu button. The usability is so bad. And if you want to change it, you need to discuss it with our UX engineer.
Please consider it again.
Comment 8•11 years ago
|
||
(In reply to Youngjun Kim from comment #7)
Hi Youngjun...
Amy and I discussed options and Amy is putting together a proposal for Wednesday Toronto time.
- Rob
Comment 9•11 years ago
|
||
(In reply to Youngjun Kim from comment #7)
> Dear Amy and Rob,
>
> If settings menu spec is revised, we need to revise UI scenario for closing
> setting menu.
> Please refer the attachment 8384930 [details].
>
> But I don't agree to change it. Because user can only close it when user
> click the setting menu button. The usability is so bad. And if you want to
> change it, you need to discuss it with our UX engineer.
>
> Please consider it again.
H Youngjun...
One thing we realized while looking at the build is that the menus are actually not working as designed and this may be contributing to the problem. When the user selects an item in the menu, the menu should close automatically and show the confirmation message. As a result, we should generally not be relying on the user to tap outside of the menu or on the view menu icon to close the menu. The only time this might be necessary if the user changes their mind and needs to back out... which is the exception as opposed to the rule. So having the full screen menus shouldn't be an issue if the menus behave as designed.
- Rob
Reporter | ||
Comment 10•11 years ago
|
||
Attachment #8379090 -
Attachment is obsolete: true
Comment 11•11 years ago
|
||
retiring madai flag, using [m+] whiteboard to track.
blocking-b2g: madai? → ---
Whiteboard: ux-tracking, visual design, jian [fxos:media] → ux-tracking, visual design, jian [fxos:media] [m+]
Assignee | ||
Comment 12•11 years ago
|
||
AFAIK this is fully resolved.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•