756246 - Changing location of context menu items

Status: RESOLVED INCOMPLETE

(Add-on SDK Graveyard :: General, defect, P2)

Description

[Siavash]

I think developers should be able to change the location of a context menu item and choose what section it goes into.

Comment 1

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

Can you provide a detailed example of what you want to do? Would being able to choose to add items to either the top of the context menu or the bottom be sufficient?

Adding the triage:followup tag to followup with the UX team.

Comment 2

[Siavash]

(In reply to Wes Kocher (:KWierso) from comment #1)
> Can you provide a detailed example of what you want to do? Would being able
> to choose to add items to either the top of the context menu or the bottom
> be sufficient?

I don't know how positioning of context menu items is done in Firefox, so I don't know how it should be done in Add-on SDK. But what I want is this:

If an item will open a new tab, for example, I should be able to put it next to "Open Link in New Tab" item, if an item will do something on selected text, I want to place it next to "Copy" item, if an item will do something to/with an image, I want to place it next to "Save Image As" or "View Image" item, and so on.

We should set the order of items, if it's possible.

And we should be able to add separators to separate the items of our add-on from other items(in the top-level context menu, not just sub-menus) and set the position of this separated section.

Comment 3

[Matteo Ferretti [:zer0] [:matteo]]

Personally, I think that this is a level of granularity we should avoid in high level APIs like context-menu: if we want to give the capability to add an item in a specific position, we should have and identifier for every possible items in every possible context menus (we have of course several context menus depends by the context), and maintain them (if a context menu item is changed or removed we have to updated our code base as well). Also, high level APIs should provide a good user experience by default, if developers can inject the item in very place could be actually be insert an item in the "wrong place".

Said that, I think what Siavash wrote in the #2 Comment could be a good trade off and also provide a better User Experience: maybe we can identify few different "area" where add the items specified by the add-on, depends by the `context` given or with an additional property.

Not sure about the separators, maybe we can add it automatically: every add-on that modify the context menu will have its separator? I doubt that will bring a good user experience… Let's see what UX says.

Comment 4

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1399562