Bugzilla – Bug 502972
ToolStripDropDownButton: whether menu should be focused and selected?
Last modified: 2009-07-16 02:54:32 UTC
bug485524 fixing make Menu comes 'focused' and 'selected' states when click it, but as Brad sad in bug457990(also have mentioned in bug477893) toolstripitem can't recieve focus , so ToolStripDropDownButton1 and ToolStripDropDownButton2 Menus in toolstripdropdownbutton.py sample shouldn't have 'focusable' state, and move mouse cursor to or click Menu shouldn't raise 'focused' but should raise 'selected', right? It make me confused now. REPRO: 1. run uia2atk/test/sample/toolstripdropdownbutton.py 2. run accerciser, expand toolbar, browse to ToolStripDropDownButton1 menu on left side, see menu's states 3. in UI, move mouse cursor to ToolStripDropDownButton1, or click it, see menu's states RESULTS: step2: ToolStripDropDownButton1 menu default has focusable state step3: ToolStripDropDownButton1 menu rise focused state EXPECTED RESULTS: ToolStripDropDownButton1 menu shouldn't have focusable and focused, but should have selected after doing step3. COMMENTS BTW, focusable and focused states of Menu doesn't affect orca to work, so I am not sure if it's necessary to remove 'focusable' and 'focused' from Menu, but it would be better to add 'selected' for Menu when select and click it
Move all P1 and P2 bugs into Release 1.1 milestone.
Just to note, this is contrary to #457990, but given recent changes by Andres, the right behavior appears to be to add Selected when focused and to add Focusable. Sorry to go back and forth on this, but there *is* a way to focus the ToolStrip (by using a keyboard shortcut), so it makes sense to add it now.
Review request: http://reviews.mono-a11y.org/r/334/
Fixed in trunk r138002 and 1.0 branch r138004.
Closed in trun rpm version: mono-uia-132785-276 uiautomationwinforms-137970-680 uiaatkbridge-138003-674 default: [STATE_ENABLED, STATE_FOCUSABLE, STATE_SELECTABLE, STATE_SENSITIVE, STATE_SHOWING, STATE_VISIBLE] click/keyboard shortcut/: +focused, +selected