Issue 123630 - [ia2] Incorrect focus event after exiting menu on menu bar opened with accelerator
Summary: [ia2] Incorrect focus event after exiting menu on menu bar opened with accele...
Alias: None
Product: General
Classification: Code
Component: accessibility (show other issues)
Version: 4.1.0-dev
Hardware: PC Windows, all
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Blocks: winA11y
  Show dependency tree
Reported: 2013-11-05 00:24 UTC by James Teh
Modified: 2013-11-07 03:51 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description James Teh 2013-11-05 00:24:40 UTC
1. Open Calc.
2. Press alt+f to open the File menu.
3. Press alt to close the menu bar.
Expected: A focus event should be fired on the now focused table cell.
Actual: A focus event is fired on the File menu item, which does not have the focused state. The now focused table cell does not have the focused state either.

Interestingly, this works correctly if you open the File menu after first activating the menu bar separately; i.e. press alt, then press f instead of pressing alt+f. Things also work correctly if you just activate the menu bar and then deactivate it without opening a menu; i.e. press alt, then press alt.
Comment 1 V Stuart Foote 2013-11-07 03:50:56 UTC
confirming on Windows 7 sp1 64-bit
AOO410m1(Build:9750)  -  Rev. 1538508

The accprobe utility running and can watch the focus events. 

Not only are the <alt>+F accelerators a bit off, but the <F6> component cycling is off as well.  

We seem to have inconsistencies in assigning focus, as all will show an MSAA accState of [focusable] but not all show as [focusable, focused...] when activating the element with <F6> movements.

Cursor key movements (U,D, L, R) and <TAB> key movements do fire focus events when navigating onto and activating element(s).