Closed
Bug 1087938
Opened 11 years ago
Closed 11 years ago
[UX] Design UX for full screen mode on link clicker UI
Categories
(Hello (Loop) :: Client, defect, P2)
Hello (Loop)
Client
Tracking
(Not tracked)
RESOLVED
FIXED
Iteration:
37.2
| backlog | Fx39? |
People
(Reporter: RT, Assigned: sevaan)
References
()
Details
(Whiteboard: [UX])
Attachments
(1 file)
We have UX for enabling the full screen mode but none for disabling it.
Updated•11 years ago
|
backlog: --- → Fx36?
Whiteboard: [ux]
Updated•11 years ago
|
backlog: Fx36? → Fx37?
Comment 1•11 years ago
|
||
high priority only as it will take 1/2 hour to get the UX and this can go to us for work.
Priority: -- → P1
| Assignee | ||
Updated•11 years ago
|
Flags: firefox-backlog+
Updated•11 years ago
|
Flags: qe-verify-
Whiteboard: [ux] → [UX]
| Assignee | ||
Updated•11 years ago
|
Points: --- → 3
Updated•11 years ago
|
Assignee: nobody → sfranks
Status: NEW → ASSIGNED
Iteration: --- → 37.2
| Assignee | ||
Comment 2•11 years ago
|
||
Attached is an image showing placement of the full-screen icon in the link clicker UIs.
When a user clicks, the content is maximized and the browser chrome is removed.
Also, the small chat window just has a pop-out mode, which can be maximized, but I've already seen user feedback asking for proper full-screen mode. I've included icon placement for this as well.
| Assignee | ||
Updated•11 years ago
|
Attachment #8534565 -
Flags: review?(rtestard)
Updated•11 years ago
|
backlog: Fx37? → Fx37+
| Reporter | ||
Comment 4•11 years ago
|
||
Based on roadmap discussions this is a Fx39 item.
backlog: Fx37+ → Fx39?
Updated•11 years ago
|
Iteration: 37.2 → 37.3
| Reporter | ||
Updated•11 years ago
|
Attachment #8534565 -
Flags: review?(rtestard) → review+
| Assignee | ||
Updated•11 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 5•11 years ago
|
||
make sure implementation bug points here - put in Fx39.
Iteration: 37.3 → 37.2
Flags: needinfo?(sescalante)
You need to log in
before you can comment on or make changes to this bug.
Description
•