Joseph,
I discovered one more thing on multiselectable widgets.
The first selection is always generating an event_object_selection event.
Subsequent selections produce EVENT_OBJECT_SELECTIONADD. That is not clear
in the spec.
I verified this behavior with Alex.
Rich
Rich Schwerdtfeger
From: Alexander Surkov <surkov.alexander@gmail.com>
To: Joseph Scheuhammer <clown@alum.mit.edu>,
Cc: Richard Schwerdtfeger/Austin/IBM@IBMUS, David Bolter
<dbolter@mozilla.com>, "W3C WAI Protocols & Formats"
<public-pfwg@w3.org>
Date: 10/29/2013 11:53 AM
Subject: Re: UAIG Test CAse 90, 91, 92 problems on MSAA/IA2
Correct.
On Tue, Oct 29, 2013 at 12:01 PM, Joseph Scheuhammer <clown@alum.mit.edu>
wrote:
> Hi Alex, Rich,
>
> A couple of questions:
>
> 1. The very same text occurs in the single selection table, where the
MSAA
> column states:
> " |EVENT_OBJECT_SELECTION| and |EVENT_OBJECT_STATECHANGE| on newly
focused
> item, but arrange events so state change does not occur on focused item,
to
> avoid extra selection change announcements
>
> Does that text vanish as well?
>
> 2. The same wording occurs in the ATK/AT-SPI columns for both the single
> selection table and the selection-follows-focus scenario of the
> multi-selection table:
> "..., but arrange events so state change does not occur on focused item,
to
> avoid extra selection change announcement."
>
> Does that text disappear too?
>
> My guess is the answers are "yes", but I want confirmation from Alex.
>
> URL to section in UAIG:
> http://www.w3.org/WAI/PF/aria-implementation/#mapping_events_selection
>
>
> --
> ;;;;joseph.
>
>
> 'A: After all, it isn't rocket science.'
> 'K: Right. It's merely computer science.'
> - J. D. Klaun -
>
