Hi, Pete. Thanks. I just wanted to be sure I understand you right. I would guess memory might be reallocated for new accessible objects so uniqueID might be not unique during life time of Firefox application. But it sounds it doesn't contradict with pool reusing.
Alex. On Thu, Feb 19, 2009 at 11:59 PM, Pete Brunet <[email protected]> wrote: > Alex, I meant during the time FF is started until it is exited. That's > obvious :-) so I should have left that out. > > 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: > Pete Brunet/Austin/i...@ibmus > Cc: > [email protected] > Date: 02/15/2009 10:48 PM > Subject: Re: [Accessibility-ia2] Scope of uniqueID > ________________________________ > > > Pete. I think it should be unique within the entire FF application. > What do you mean by full session? Do you mean accessible object might > have uniqueID previously assigned to destroyed accessible object or > something else? > > Alex. > > > On Sat, Feb 14, 2009 at 9:48 AM, Pete Brunet <[email protected]> wrote: >> Is it unique within the entire FF application and for the full session? >> >> I also asked Xing Li regarding Symphony. >> >> What I was thinking when I wrote this text was that it would be unique >> within a frame, e.g. a single app might be able to activate more than one >> client area wrapped with some chrome, or parts of the app might able to be >> undocked, or dialogs popped up. From the perspective of the app >> developer, >> what is the largest scope within which uniqueness could be managed? And >> how >> would you describe that environment? >> >> 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: Aaron Leventhal <[email protected]> >> To: Alexander Surkov <[email protected]> >> Cc: Pete Brunet/Austin/i...@ibmus, Aaron M Leventhal/Cambridge/i...@ibmus, >> [email protected] >> Date: 02/13/2009 04:25 PM >> Subject: Re: [Accessibility-ia2] Scope of uniqueID >> ________________________________ >> >> >> 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 >> >> > > > > _______________________________________________ > 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
