This is being forked off of bug 1325758 comment 6. If possible it would be nice to get the context menus inserted in a consistent order. Currently I'm assuming its based on when chrome.contextMenus.create gets called by the add-on. Perhaps we could make it so its sorted on the add-on installation order. Alphabetically is all well and good until you go to different locales.
> Currently I'm assuming its based on when chrome.contextMenus.create gets > called by the add-on. I believe it's even weirder, based on the *first time* .create() is called by the addon since browser startup. > Perhaps we could make it so its sorted on the add-on installation order. > Alphabetically is all well and good until you go to different locales. Alphabetically is still consistent in any locale, so IMO it's is a good solution if we want to go that way. We might wanna align what we use here with the Jazz thing. In any case, UX would probably have something to say here.
As of right now, it's a mess as you don't know what will load first during startup. It would be nicer it developers / users can insert separators. This should be P3.
Mike Conca and I had a discussion about this and related context-menu issues at the Austin All Hands. Based on that discussion, which was encouraging, I am hopeful that we can make progress on these issues. One of the use cases we discussed was an extension which might like to make additional search engines (beyond the default) available in the context menu, like Context Search. I use such an extension very heavily, to look up terms I encounter on Wikipedia, Wiktionary, etc., and I imagine there are a number of other users who do as well. There are several issues impeding the user experience with such an extension currently: - The insertion point of the context menu is currently unpredictable (i.e., this bug). This inhibits the development of muscle memory to use a particular entry. - Even if the insertion order is made predictable, always adding extension entries at the bottom can result in the set of context menu entries not being in a logical / consistent order. For example, a search-related context menu entry would make much more sense next to the existing "search with the default search engine" entry, than at the bottom of the menu. One idea brought up during the discussion was giving each "section" of the context menu (the groups separated by horizontal bars) a name, and allowing extensions to choose a section to be inserted into. - The limitation that one extension can only have one top-level context menu entry means that either: a) the individual search engines are in a submenu (even worse for muscle memory since you now have to hover, pause, move the mouse precisely sideways, etc.); or b) you install a separate extension for every search engine you want there. It would be nice not to have to resort to such workarounds. Mike, I am needinfo-ing you as requested in Austin. Please let me know if there is anything I can do to help make progress / achieve a resolution on these issues. Thanks!
You need to log in before you can comment on or make changes to this bug.