[Accessibility-ia2] next changes to IAccessible2

[Alexander Surkov]

Hi, Jamie and Pete.

My suggestion was based on assumption that AT always knows what they
need, i.e. if they need explicit name then they get explicit name, if
they need computed name then they get computed name. In other words
they don't need to know whether this name is explicit or computed. If
AT needs that then I agree the flag is more suitable for that,
otherwise they need to compare strings what's not a way to go.

If you think the flag is preferable then I'm fine to change it (or
feel free to edit wiki yourself).

Thank you.
Alex.


On Wed, Jun 8, 2011 at 8:07 AM, James Teh <jamie at nvaccess.org> wrote:
> On 8/06/2011 7:46 AM, Peter Korn wrote:
>>     * Regarding the explicit name
>>       <https://wiki.mozilla.org/Accessibility/IA2_1.3#Explicit_name>
>>       idea, what about a simple property indicating whether the name was
>>       explicitly set vs. derived automatically?
> In principle, I prefer that to another name retrieval property. It seems
> redundant to implement two name retrieval properties that will return
> the same thing in many cases (and explicitName will return NULL whenever
> they are different).
>
> That said, having to check an additional property does mean an extra
> call, which will have a slight performance impact. Even so, the AT will
> probably need the name regardless, even if it treats it differently
> based on whether it is "explicit".
>
> Jamie
>
> --
> James Teh
> Vice President, Developer
> NV Access Inc, ABN 61773362390
> Email: jamie at nvaccess.org
> Web site: http://www.nvaccess.org/
> _______________________________________________
> Accessibility-ia2 mailing list
> Accessibility-ia2 at lists.linuxfoundation.org
> https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
>