just in case, bug URLS are: https://bugs.linuxfoundation.org/show_bug.cgi?id=436 https://bugs.linuxfoundation.org/show_bug.cgi?id=437
On Tue, Apr 20, 2010 at 3:02 PM, Pete Brunet <[email protected]> wrote: > Thanks for starting that discussion Car, I opened the following. Please > review: > - deprecate IA2_TEXT_BOUNDARY_ALL > http://bugs.freestandards.org/show_bug.cgi?id=436 > - mention IA2_TEXT_OFFSET_LENGTH (-1) in the methods it applies to > http://bugs.freestandards.org/show_bug.cgi?id=437 > > Thanks, Pete > > Carolyn MacLeod wrote: > > > Interesting - thanks for pointing this out! > I didn't notice the "special offsets" section: > http://accessibility.linuxfoundation.org/a11yspecs/ia2/docs/html/_generalinfo.html#_specialOffsets > (actually, I think I read this once a long time ago, but now that I am > implementing, I am reading method by method. Might be nice to point to this > in the method doc for each of the 10 methods it applies to, i.e. "See also > [special offsets link]"). > > So there are currently 5 ways to get the whole text... even more reason to > deprecate IA2_TEXT_BOUNDARY_ALL. :) > > Carolyn > > > > *Re: [Accessibility-ia2] Deprecate IA2_TEXT_BOUNDARY_ALL?* > *Michael Curran * to: Accessibility-ia2 > 04/15/2010 07:29 PM > > Sent by: *[email protected] > <[email protected]>* > > > > > ------------------------------ > > > > I'm pretty sure that NVDA sometimes makes use of > IAccessible::text(0,IA2_TEXT_OFFSET_LENGTH,text) > > Where IA2_TEXT_OFFSET_LENGTH is -1. > > I'm not sure when this was introduced to IA2, but Gecko supports it, not > sure about Symphony. > > Very useful as it stops the need for calling nCharacters. > > Mick > > On 16/04/2010 7:40 AM, James Teh wrote: > > On 16/04/2010 2:39 AM, Carolyn MacLeod wrote: > >> Do AT's use IA2_TEXT_BOUNDARY_ALL? > > We don't. However, see below. > > > >> Or do they use IAccessibleText::text(0, length, pbstrText) to retrieve > >> all of the text? > > We do this. > > > >> 2) Technically, we don't need it because IAccessibleText::text(0, > >> length, pbstrText) already returns the whole text. > > Note that this requires ATs to make an extra call > > (IAccessibleText::nCharacters) to determine the length. Extra calls do > > matter across process boundaries. We do this anyway, but it's worth > > adding to the discussion. > > > >> I am tempted to return E_INVALIDARG if get boundaryType == > >> IA2_TEXT_BOUNDARY_ALL in textAfterOffset and textBeforeOffset. Would > >> that break anybody? > > Hmm. That makes it look like the caller is wrong to try to use it when > > it is in the spec. I'd prefer E_NOTIMPL, but I realise that's only > > supposed to be used when the entire method isn't implemented. Are there > > any other options that indicate that this particular request isn't > > implemented? > > > > Jamie > > > > -- > Michael Curran > email/msn/jabber: [email protected] > Skype/Twitter: md_curran > _______________________________________________ > Accessibility-ia2 mailing list > [email protected] > https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2 > > ------------------------------ > > _______________________________________________ > Accessibility-ia2 mailing > [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.linuxfoundation.org/mailman/listinfo/accessibility-ia2
