This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7118 - 4.5 determine if Mac and Linux have menu events comparable to the MSAA events in 4.5
Summary: 4.5 determine if Mac and Linux have menu events comparable to the MSAA events...
Status: RESOLVED FIXED
Alias: None
Product: ARIA
Classification: Unclassified
Component: Core AAM (show other bugs)
Version: 1.0
Hardware: PC Linux
: P1 normal
Target Milestone: ---
Assignee: David Bolter
QA Contact: ARIA UA Implementors
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-17 12:22 UTC by Andi Snow-Weaver
Modified: 2010-07-01 19:42 UTC (History)
0 users

See Also:


Attachments

Description Andi Snow-Weaver 2009-07-17 12:22:03 UTC
 
Comment 1 David Bolter 2009-09-14 18:55:52 UTC
Did some research here...

Windows:

OK so the MSAA events for menus normally go:

EVENT_SYSTEM_MENU (START, POPUPSTART, POPUPEND, END).

For ARIA test case:
http://archive.dojotoolkit.org/dojo-2009-09-14/dojotoolkit/dijit/tests/test_Menu.html

FF only seems to fire the POPUPSTART and POPUPEND.

Linux:

There are no special events with "menu" in the name.

Generally these events are used, and roles can be inspected to discern them as menu events:

focus: and object:state-changed:selected for menu.
menu also emits object:selection-changed when you arrow through the menu items inside.

Mac:

no data yet.
Comment 2 Andi Snow-Weaver 2009-09-15 16:28:59 UTC
David to check to see what FF does if a popup menu is displayed, focus moves away from it but it doesn't disappear, and then focus moves back to it.

Once have test case, pass this to Cynthia to check IE.
Comment 3 Andi Snow-Weaver 2009-09-15 18:03:30 UTC
Why do screen readers ignore focus events when a menu is open? 

David thinks maybe they track selection events?

Andi to check with Rich (or Aaron). 
Comment 4 Andi Snow-Weaver 2010-01-25 17:47:08 UTC
I checked with Aaron about the screen readers ignoring focus events. It's only Windows screen readers that do this and he has no idea why. Because of this, menuing (on Windows) is very fragile so that's why the propoer nesting of the events is so important.
Comment 5 David Bolter 2010-02-16 14:30:11 UTC
(In reply to comment #4)
> I checked with Aaron about the screen readers ignoring focus events. It's only
> Windows screen readers that do this and he has no idea why. Because of this,
> menuing (on Windows) is very fragile so that's why the propoer nesting of the
> events is so important.
> 

Not all Windows screen readers ignore focus; in fact paying attention to focus first and foremost seems to be very resilient.
Comment 6 David Bolter 2010-02-25 09:17:58 UTC
James tells me the OSX events should be:
kAXMenuOpenedNotification
kAXMenuClosedNotification
kAXMenuItemSelectedNotification
Comment 7 David Bolter 2010-02-25 16:09:15 UTC
Oh those are not necessarily in order :/
Comment 8 Andi Snow-Weaver 2010-03-02 15:42:12 UTC
Add Mac events to the table.
Comment 9 Andi Snow-Weaver 2010-04-21 18:39:09 UTC
Added Mac events to the table. 

David, please review in the editor's draft:

http://www.w3.org/WAI/PF/aria-implementation/#mapping_events_menus
Comment 10 David Bolter 2010-05-04 14:30:00 UTC
(In reply to comment #9)
> Added Mac events to the table. 
> 
> David, please review in the editor's draft:
> 
> http://www.w3.org/WAI/PF/aria-implementation/#mapping_events_menus

Looks OK to me. Would be good to have Apple on the calls ;)