The apparent reason for this new method is for performance, i.e. the AT can already walk up the tree looking for a role of interest. Has there been a situation where walking up the tree is causing a performance problem? In my experience, AT (at least some AT) are constantly walking up and down the tree, and I haven't noticed a performance issue. Also, as Jamie implies, you'd only have to walk the tree once to find the parent of interest and then save a reference to it. I just want to make sure we are solving a real problem before inflating IA2. -Pete
On 2/22/12 4:27 PM, James Teh wrote: > On 22/02/2012 6:54 PM, Alexander Surkov wrote: >> The proposed document accessible concept is close to DOM document. ... >> One example was get_accChild that can return child accessible >> by uniqueID. > True, though the only time you ever need that is to test whether a > given node is within a document. If you are trying to do that, you > probably already have a reference to the document accessible. > >> All caret/selection methods are >> fast on document accessible and slow on child accessible. > But in that case, we're probably dealing with an editable document, > which is a real ROLE_SYSTEM_DOCUMENT object. Trying to query for caret > or selection on an application or frame just doesn't make sense. > >> Theoretically anchorTarget is applicable to any document type, >> requirement is the URL should contain '#' pointing to element. > Technically, that's true, but I don't see any use case for this in the > wild. Why would an AT want to query for anchor target on an application? > > The problem is that all of this is abusing the idea of a document > property. In Gecko, an application might be the same internally as a > document, but that's not true from a user (and probably AT) perspective. > > One option is to note that the document property just returns the > nearest document. If necessary, add a note stating that this will > usually be a ROLE_SYSTEM_DOCUMENT accessible, but that the definition > of document depends on the application. This makes a little trickier > for clients to know what they'll get, but it does allow for a bit of > flexibility. > > Jamie > _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
