It appears the relations were moved to the new ia22 interface. Is that why you 
are deprecating the relations interface?

Sent from my iPad

On Feb 4, 2013, at 10:15 PM, "Richard Schwerdtfeger" <sch...@us.ibm.com> wrote:

> Whe are relations deprecated? They are used extensively in both FF, Chrome, 
> and Symphony.
> 
> Rich
> 
> Sent from my iPad
> 
> On Feb 4, 2013, at 8:32 PM, "Pete Brunet" <p...@a11ysoft.com> wrote:
> 
>> 
>> On 10/10/12 1:29 AM, James Teh wrote:
>>> Hi all, 
>>> 
>>> Sorry for taking so long. Here is my feedback: 
>>> 
>>> Accessible2.idl: 
>>> IAccessible2 has been removed from the Interfaces section. It should still 
>>> be included. (I see Pete has already acknowledged this.) 
>>> I'm not sure it makes sense to say the older interfaces (except 
>>> IAccessibleTable, which has essentially been completely replaced) are 
>>> deprecated, as the newer ones subclass them.
>> I've removed the deprecated text from IAHypertext and IAText.  I think it 
>> still make sense to indicate IARelation is deprecated.
>>> The IAccessible2 interface still contains the modifications relevant to 
>>> IAccessible2_2. Specifically, the max parameters for extendedStates and 
>>> localizedExtendedStates have been removed and the new methods attribute, 
>>> accessibleWithCaret and relationTargetsOfType have been added. I assume 
>>> this was unintentional in this latest version. This critical, as it will    
>>>    breka binary compatibility.
>> Yes, That was unintentional.  I diffed the old and new IAccessible2 and 
>> fixed the problems.
>>> 
>>> 
>>> AccessibleDocument.idl: 
>>> Regarding IAccessibleDocument::anchorTarget, I wonder whether a relation 
>>> fits here, which would eliminate the need for this interface. I think this 
>>> was discussed before, but I can't remember why this idea was dropped. After 
>>> all, it just returns an accessible.
>> Back on 12 Feb 12 you said:
>> I feel a relation "fits" well enough here, but I don't feel strongly enough 
>> about it to fight for it if others disagree. I'd pose the question: what 
>> makes this so special as to justify a new method? Why is it more special 
>> than, say, flowsTo or labelledBy? I guess it doesn't fit relations entirely, 
>> as it isn't strictly "related" so much as state information. If that 
>> argument is consensus, fair enough. 
>> And I responded:
>> Thanks Jamie, It appears there is no strong preference by anyone for any of 
>> the various options.  Your observation about state vs relationship is 
>> interesting and is enough to motivate me to choose a method over a relation.
>>> 
>>> AccessibleHypertext2.idl: 
>>> The comments for the IAccessibleHypertext2 interface say: 
>>>  The %IAccessibleHypertext interface is the main interface to expose 
>>>   hyperlinks in a document, typically a text document... 
>>> This is a bit confusing, as this documentation is for 
>>> IAccessibleHypertext2, not IAccessibleHypertext. It should probably just 
>>> mention that this extends IAccessibleHypertext.       
>>> The same goes for IAccessibleText2.
>> Thanks Jamie, I fixed that.
>>> 
>>> I'll reply to Alex's feedback separately. 
>>> 
>>> Thanks, 
>>> Jamie 
>>> 
>>> On 21/09/2012 12:22 PM, Pete Brunet wrote: 
>>>> I finished up the IA2 1.3 work over the weekend but due to some changes 
>>>> on the LF web site am unable to post it there.  I've provided it at 
>>>> a11ysoft.com.  Please review it.  I won't get to the object attributes 
>>>> until later (to add explicit-name). 
>>>> 
>>>> documentation: http://a11ysoft.com/ia2/docs/html 
>>>> zip file: http://a11ysoft.com/ia2.zip 
>>>> 
>>>> The one bug I see so far is that I don't have a link for the 
>>>> IAccessible2 interface on the main page.  That is at: 
>>>> http://www.a11ysoft.com/ia2/docs/html/interface_i_accessible2.html 
>>>> 
>>>> The zip file contains everything I'll eventually post on the LF site, 
>>>> among other things, changelog.txt and the merged IDL file, 
>>>> ia2_api_all.idl. 
>>>> 
>>>> Pete 
>>>> -- 
>>>> *Pete Brunet* 
>>>> 
>>>> a11ysoft - Accessibility Architecture and Development 
>>>> (512) 467-4706 (work), (512) 689-4155 (cell) 
>>>> Skype: pete.brunet 
>>>> IM: ptbrunet (AOL, Google), ptbru...@live.com (MSN) 
>>>> http://www.a11ysoft.com/about/ 
>>>> Ionosphere: WS4G 
>>>> 
>>>> 
>>>> _______________________________________________ 
>>>> Accessibility-ia2 mailing list 
>>>> Accessibility-ia2@lists.linuxfoundation.org 
>>>> 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), ptbru...@live.com (MSN)
>> http://www.a11ysoft.com/about/
>> Ionosphere: WS4G 
>>  _______________________________________________
>> Accessibility-ia2 mailing list
>> Accessibility-ia2@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
> _______________________________________________
> Accessibility-ia2 mailing list
> Accessibility-ia2@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
_______________________________________________
Accessibility-ia2 mailing list
Accessibility-ia2@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2

Reply via email to