I don't mind adding the method to the spec but I don't have strong opinion either. I agree with Jamie that keeping the text method on IAccessible2 looks unusual. In Gecko we keep an analogue method in text interface: int32_t GetChildOffset(Accessible* aChild);
Alex. On Tue, Feb 26, 2013 at 12:29 PM, James Teh <[email protected]> wrote: > Unusually :), I find it difficult to give an opinion on this. Clearly, > multiple people think it should be introduced. However, I find it very hard > to justify introducing what is essentially a hack into the main IAccessible2 > interface. Furthermore, this method is related to IAccessibleText, yet it's > not in a text specific interface. Once it's in the main interface, it can't > be removed and server implementers have to implement it, even if they just > throw not implemented. If it must be introduced, I'd prefer to see a > separate interface for it, but that seems rather silly. In short, I'm not > going to fight inclusion of this, since I don't have strong enough arguments > against, but I'm not entirely comfortable with it either. > > Jamie > > > On 26/02/2013 7:50 AM, Pete Brunet wrote: >> >> Alex, Brett, Jamie, What do you recommend? >> >> 1) HRESULT IAccessible2_2::offsetInParentText ( >> [out] long* offset >> ); >> >> Return the text offset in the immediate parent node. >> >> 2) Do not add this method. >> >> 3) Something else. >> >> Pete >> >> On 2/10/13 8:15 PM, Alexander Surkov wrote: >>>> >>>> It's a total hack. However, imo, this whole idea is a hack. :) >>> >>> It could be. IAccessibleHyperlink or IAccessibleText on text leafs are >>> hacks and actually it is a thin ice for Firefox. This easily could >>> face us to lot of work. Also these approaches aren't really subject of >>> the spec and it should introduce even bigger difference in >>> implementations between servers. >>> >>> On the another hand we have the method on internal layer in Firefox >>> that Brett needs. The method is used to build >>> IAccessibleText/Hypertext implementation from accessible tree. So if >>> AT works both with accessible tree and IAccesisbleText/HyperText for >>> text stuff then this method can be useful. >>> >>> Thank you. >>> Alex. >>> >>> >>> On Mon, Feb 11, 2013 at 11:00 AM, James Teh<[email protected]> wrote: >>>> >>>> On 11/02/2013 11:22 AM, Alexander Surkov wrote: >>>>> >>>>> Hi, Jamie. If text leafs implement IAccessibleHyperlink but previously >>>>> IAccessibleHyperlink was implemented by embedded objects only then >>>>> this might be something that AT relies on. >>>> >>>> I guess this is a possibility, though I'd assume that ATs that don't >>>> need >>>> text leaf nodes wouldn't traverse them. We'd certainly need ot check, >>>> though. >>>> >>>> >>>>> On the another hand parent >>>>> IAccessibleHyperText would return a collection of children instead the >>>>> collection of embedded objects and AT could have dependencies on it as >>>>> well. >>>> >>>> Ah. I was imagining that the parent IAccessibleHypertext wouldn't return >>>> the >>>> text leaf nodes. See notes on hack below. >>>> >>>> >>>>> pure IAccessibleHyperlink on text leafs >>>>> is rather a hack than it suites them well. >>>> >>>> It's a total hack. However, imo, this whole idea is a hack. :) >>>> >>>> >>>> Jamie >>>> >>>> -- >>>> James Teh >>>> Director, NV Access Limited >>>> Email:[email protected] >>>> Web site:http://www.nvaccess.org/ >>>> Phone: +61 7 5667 8372 >>>> _______________________________________________ >>>> Accessibility-ia2 mailing list >>>> [email protected] >>>> https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2 >>> >>> _______________________________________________ >>> Accessibility-ia2 mailing list >>> [email protected] >>> https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2 >>> >> >> -- >> *Pete Brunet* >> >> >> a11ysoft - Accessibility Architecture and Development >> (512) 467-4706 (work), (512) 689-4155 (cell) >> Skype: pete.brunet >> IM: ptbrunet (AOL, Google), [email protected] (MSN) >> http://www.a11ysoft.com/about/ >> Ionosphere: WS4G > > > -- > James Teh > Director, NV Access Limited > Email: [email protected] > Web site: http://www.nvaccess.org/ > Phone: +61 7 5667 8372 > _______________________________________________ > Accessibility-ia2 mailing list > [email protected] > https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2 _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
