On 3/12/2015 6:20 AM, Alexander Surkov wrote:
Right, that's unfortunate but ATK and IA2 differ. If I remember
Joanie's words then ATK state has been introduced a while ago and used
somewhere in GTK. Same is more or less valid for IA2. As Jamie said
IA2 can be changed but we need to make sure nobody depends on the
implementation.
IMO, even the wording for the ATK active state is misleading, but that's
an entirely different issue and it's not really relevant because
everyone in ATK land knows what it means. :)
On the other hand it's probably ok to not sync ATK and IA2 for this
particular case. IA2 has a way for a fast way to obtain object
attributes, so perfromance is not an issue for IA2 unlike ATK, thus
IA2 doesn't necessary need a state in addition to the object attribute.
Not necessarily, but using object attributes for things that should
probably really be states is also pretty ugly. :) As for "a fast way to
obtain object attributes", that's controversial. We can either obtain
one or all. All is slow on the server side, while one requires far too
many calls, which is hideous for an out-proc client. Out-proc clients
are actually better off fetching all states because the server side
penalty is far less than the penalty of multiple cross-proc calls.
Jamie
--
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: [email protected]
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
