My understanding is:
1) FF uses the address of the object and that it's unique within the app
and even within the machine.
2) NVDA needs uniqueness in the machine.
I believe this would work for other ATs as well.
I am waiting for input from Xing Li regarding what Symphony does.
My original understanding was that the number would be unique within an
application. I provided the following in the spec, but you can see this
will not work to define uniqueness within the machine.
One means of implementing this would be to create a factory with a 32 bit
number generator and a reuse pool. The number generator would emit numbers
starting at 1. Each time an object's life cycle ended, its number would be
saved into a resuse pool. The number generator would be used whenever the
reuse pool was empty.
The above assumes that the AT is notified when objects end their life so
the reuse of a uniqueID is not an issue.
Pete Brunet
IBM Accessibility Architecture and Development
11501 Burnet Road, MS 9022E004, Austin, TX 78758
Voice: (512) 286-5485, Cell: (512) 689-4155
Ionosphere: WS4G
From:
Alexander Surkov <[email protected]>
To:
Aaron Leventhal <[email protected]>
Cc:
Pete Brunet/Austin/i...@ibmus, Aaron M Leventhal/Cambridge/i...@ibmus,
[email protected]
Date:
02/15/2009 10:43 PM
Subject:
Re: [Accessibility-ia2] Scope of uniqueID
Hi, Aaron. I misread the code. You're right, we expose unique ID for
different accessible objects. Sorry for noise.
Alex.
On Sat, Feb 14, 2009 at 6:24 AM, Aaron Leventhal <[email protected]>
wrote:
> Alex,
>
> Is there a bug filed for that?
>
> As far as I know, if several accessible objects share the same DOM node,
we
> use a different pointer (from the internal accessible object itself),
thus
> avoiding any issues.
>
> So, unless you know of particular issues, I think we're fine.
>
> - Aaron
>
> On 2/13/2009 4:41 AM, Alexander Surkov wrote:
>
> Hi. uniqueID in Firefox is formed from memory address of DOM element
> the accessible object is created for. It means uniqueness of uniqueID
> doesn't depend on window. On another hand it's not unique at all for
> some accessibles (some accessibles share the same DOM element) but
> it's Firefox bug I think.
>
> Alex.
>
>
> On Fri, Feb 13, 2009 at 4:50 AM, Pete Brunet <[email protected]> wrote:
>
>
> From Jamie in another thread:
>
> ...(if I recall correctly) uniqueID is only unique within a given hwnd.
>
> The spec says:
>
> The uniqueID is an identifier for this object, is unique within the
current
> window, and remains the same for the lifetime of the accessible object.
>
> The uniqueID is not related to the MSAA objectID which is used by the
server
> to disambiguate between IAccessibles per HWND or the MSAA childID which
is
> used to disambiguate between children being managed by an IAccessible.
>
> I don't remember a discussion about uniqueID being unique per each HWND.
> Perhaps the wording "unique within the current window" could be
improved.
> Does anyone have a suggestion?
>
> Also what assumption have people already made about uniqueIDs?
>
> Pete Brunet
>
> IBM Accessibility Architecture and Development
> 11501 Burnet Road, MS 9022E004, Austin, TX 78758
> Voice: (512) 286-5485, Cell: (512) 689-4155
> Ionosphere: WS4G
>
> _______________________________________________
> Accessibility-ia2 mailing list
> [email protected]
> https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
>
>
>
>
> _______________________________________________
> Accessibility-ia2 mailing list
> [email protected]
> https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
>
>
>
>
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
