Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 366447

Summary: [commands] consider using context menus instead of dropdown button when menu group is textless
Product: [ECD] Orion Reporter: Susan McCourt <susan>
Component: ClientAssignee: Susan McCourt <susan>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 0.3   
Target Milestone: 0.4 RC1   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Susan McCourt CLA 2011-12-12 13:51:28 EST 
When a group of menu commands has no text, we want to use a button/gear menu to invoke the menu.  At this point, the button is really behaving as a context menu trigger.  There's no reason for us to use dijit.DropDownButton in these cases because we're not trying to position the menu directly under the invoking button.  It would simplify the code (and styling!) if we instead create our normal command span with an image and just bring up a context menu when it's clicked.
Comment 1 Susan McCourt CLA 2011-12-14 13:55:13 EST 
The down side of dropping DropDownButton is that it provides free tab traversal and activation on the space key.  I should probably try harder at styling it appropriately.  What I want is the same look as image commands, with a border and hover shading.
Comment 2 Susan McCourt CLA 2012-02-21 12:18:59 EST 
we fixed the icon, styling, hover effect in RC1.
No need to change the implementation.