I see, apparently I worked with out of dated ATK spec which didn't say about non windows :)
I sent a question to Joanie in the previous email. ATK has object attribute change event iirc. On Mon, Aug 31, 2015 at 4:36 PM, Joseph Scheuhammer <[email protected]> wrote: > Hi Alex, > > I agree on 'current' object attribute, not sure ACTIVE_STATE is a proper >> mapping for both IA2 and ATK (ATK defines it as "Indicates a window is >> currently the active window"). Why do you think it's worth to set up the >> state? >> > > Short answer: because Joanie told me so. :-) > > Longer answer: the documentation for ACTIVE_STATE says more than just the > currently active window . It also notes: > - It is used to indicate the active subelement within a container. > - It is *not* used to indicate focus. Use STATE_FOCUSED to indicate focus. > - It is *not* used to indicate selection. Use STATE_SELECTED to indicate > selection. > > See > https://developer.gnome.org/atk/unstable/atk-AtkState.html#AtkStateType. > You'll have to scroll down to and look for ATK_STATE_ACTIVE since there is > no direct link. > > Also, the state is useful for state change events. See: > http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#event-aria-current. > I should have pointed to the event mappings in my last email since they the > IA2 mappings need confirmation there too. > > Thanks. > > > -- > ;;;;joseph. > > 'Array(16).join("wat" - 1) + " Batman!"' > - G. Bernhardt - > >
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
