Closed
Bug 855305
Opened 12 years ago
Closed 12 years ago
Give the menu panel multiple customization areas
Categories
(Firefox :: Toolbars and Customization, defect)
Firefox
Toolbars and Customization
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mconley, Unassigned)
References
Details
According to UX, we want 2 customization areas in the menu panel. And they're not exactly equal.
There should be an area "A" at the top of the panel that allows for "wide" widgets, like the search input, cut/copy/paste and -/100%/+. There might be others, but these are the ones I know about.
The second area "B" is for "buttons". These widgets take up a single slot in the grid, or a single row when in list view.
If I understand UX's design properly, I don't believe widgets that go into A can go into B, or vice versa.
Reporter | ||
Comment 1•12 years ago
|
||
This is definitely not making it to M2.
Comment 2•12 years ago
|
||
Widgets created via the API already support defining restrictions on where they can be placed, via the allowedAreas property. Currently that's an array of area IDs, but I think it should actually be an array of area *types*. ie, main-toolbar, secondary-toolbar, panel, panel-special.
It should be pretty simple to add the same kind of restriction to areas, such that the area's properties can define a restriction on what kind of widgets are allowed to be placed there. Easiest way would be to do it via the |type| property.
That's the easy part.
The hard part is figuring out what the UX side of it is, because it's going to feel like an artificial limitation.
Reporter | ||
Comment 3•12 years ago
|
||
At least as far as I understand, this is no longer a requirement. The "fat" widgets (Edit and Zoom widgets) should just fill in a whole row's worth of space in the menu panel. A special area for them is not required.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Comment 4•12 years ago
|
||
Er, does that mean you'd be able to have normal icon-sized widgets both above and below the wide edit/zoom widgets?
You need to log in
before you can comment on or make changes to this bug.
Description
•