Closed
Bug 756042
Opened 13 years ago
Closed 13 years ago
Grouping context menu items [suggestion]
Categories
(Add-on SDK Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: siavash.askari.nasr, Unassigned)
Details
Developers should be able to group their menu items and put the items in a sub-menu.
It should be in a way that developers could use it as a preference, so that users can decide whether or not to group items.
I think I didn't explain it clearly. What I'm saying is, based on a boolean value(for example) all menu items would be grouped or ungrouped, automatically.
Could you explain this a bit better? Developers can already nest context menu items in submenus.
Would this be a user-facing preference to just nest everything or nest nothing?
Whiteboard: [triage:followup]
In Google Chrome extensions, if an add-on has more than one context menu item, Chrome will put them in a sub-menu.
From Google Chrome Extensions:
"You can create as many context menu items as you need, but if more than one from your extension is visible at once, Google Chrome automatically collapses them into a single parent menu."
But it is a forced behavior, so I'm suggesting this feature, with an option to let users decide whether or not to nest all items of an add-on.
Comment 4•13 years ago
|
||
So, currently we have designed it so that the developer can create groups or just context menu items and we like the flexibility in that. Adding that kind of complexity to the user is something that a developer could achieve now, but we (the project drivers) don't want that kind of user complexity to be the default - as this is already a complicated thing to describe, it would be doubly so for a user faced with the choice.
Since it is possible to create this in code, we are going to wontfix this bug
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Whiteboard: [triage:followup]
You need to log in
before you can comment on or make changes to this bug.
Description
•