Community
Participate
Working Groups
We currently do not show command tooltips when the command is rendered as a dojo menuitem. It turns out that some of these commands (Export/import to various places, etc.) are the ones that could most use it. In order to have tooltips, we need to programmatically create the tooltip and attach it to the menu item as its created, or else come up with a scheme for automatic creation in our own menuitem. This is something we should be careful about doing from an overhead point of view, and is probably best looked at in the context of bug 338888.
*** Bug 359974 has been marked as a duplicate of this bug. ***
(In reply to comment #0) > It turns out that some of these commands (Export/import to > various places, etc.) are the ones that could most use it. I found myself wondering which branch was which when using the "rebase" menu and had to go to the code to read the tooltip. This led me to investigate the true performance impact of tooltips. It is not noticeable speed wise when loading a large navigator, and the tooltip is reused. When you use the "More" menus, you get a new menu for every row that you hover, but only one tooltip that is repurposed for the various menus and menuitems. Given this, I have released the menu tooltip support for 0.3. I still find the dojo tooltips clunky, and it's easy to get one "stuck" on and have to click to dismiss it. But I do find the info helpful... fixed with 84abf01fa335a3613f5147248046a1fc7d3aaa1a
