Allow extensions to modify tabstrip context menu |
|||
Issue descriptionExtensions can currently modify content area context menus and the context menus of app icons in the launcher/taskbar/doc. It would be useful for extensions to be able to modify other context menus in Chrome, in particular the tabstrip context menu. Bug 515930 discusses removing some tabstrip context menu items. Especially if we do this, we'd like extensions to be able to remedy the lack. Even without it, we'd like extensions to be able to provide advanced functionality (suggestions elsewhere include things like "close tabs opened by this one"). The relevant docs are at https://developer.chrome.com/extensions/contextMenus . The easiest way I see would be to add a new value, "tab", to the ContextType enum, and exclude it from "all" (similar to how "launcher" is handled). There may be other, better ways to do this. Alternate proposals welcome.
,
Mar 24 2017
I think this would be reasonably easy to implement, if the proposed change is acceptable. I may be willing to drive this. My concern about my proposal is with scaling: there are many other chrome-side context menus, and "all" will become increasingly inaccurate over time if we add more names here. We could rename "all" as "content" (and, if desired, introduce "chrome" to mean "non-content", but I'm not sure that makes sense to do?). Of course we'd probably have to do this by deprecating "all" and parsing it as "content" when found.
,
Jun 29 2017
,
Jul 2
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 6
Peter, do you still have any interest in this?
,
Jul 6
I still think this is worth doing, yes.
,
Jul 6
Any interest in driving it, or know any volunteers? I'm still on board, but likely won't have the bandwidth in the immediate future. Otherwise, we can just leave this as available for anyone interested.
,
Jul 6
I think we're going to have to leave it on the table unless someone external steps up. I don't have the bandwidth. |
|||
►
Sign in to add a comment |
|||
Comment 1 by rdevlin....@chromium.org
, Mar 24 2017