Open
Bug 1389656
Opened 7 years ago
Updated 2 years ago
The nav-bar is cut off (dynamic overflow is disabled) when in customize mode, hiding toolbar buttons at the end of the toolbar
Categories
(Firefox :: Toolbars and Customization, defect, P5)
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox57 | --- | affected |
People
(Reporter: alice0775, Unassigned)
References
Details
(Keywords: dupeme, ux-consistency, Whiteboard: [reserve-photon-structure] )
Attachments
(1 file)
|
76.28 KB,
image/png
|
Details |
bug.screenshot
Reproducible: always Steps To Reproduce: 1. Put some toolbar buttons on Navbar 2. Enter customize mode Actual Results: Some toolbar button is missing due to overflow. See attached screenshot Expected Results: The overflowed buttons should appear in upper pane of overflow panel even if customize mode
|
Reporter | |
Updated•7 years ago
|
Whiteboard: [DUPEME] → [photon-structure][DUPEME]
|
|
Reporter | |
Updated•7 years ago
|
Summary: Some toolbar button is missing when enter customize mode → Some overflowed toolbar button is missing when enter customize mode
|
||
Comment 1•7 years ago
|
||
Can you confirm my suggested summary is still correct? Am I right in thinking this is also an issue on stable (though of course, there we don't show the overflow panel in customize mode) ?
Flags: needinfo?(alice0775)
Summary: Some overflowed toolbar button is missing when enter customize mode → The nav-bar is cut off (dynamic overflow is disabled) when in customize mode, hiding toolbar buttons at the end of the toolbar
Whiteboard: [photon-structure][DUPEME] → [photon-structure][triage][DUPEME]
|
||
Updated•7 years ago
|
Priority: -- → P4
Whiteboard: [photon-structure][triage][DUPEME] → [reserve-photon-structure] [DUPEME]
|
|
||
Updated•7 years ago
|
Priority: P4 → P5
|
|
||
Updated•7 years ago
|
Flags: a11y-review+
QA Contact: gwimberly
|
||
Updated•2 years ago
|
Severity: normal → S3
|
||
Updated•2 years ago
|
Keywords: dupeme
Whiteboard: [reserve-photon-structure] [DUPEME] → [reserve-photon-structure]
You need to log in
before you can comment on or make changes to this bug.
Description
•