Btw, we could change the comment of IAccessibleHyperLink and consider action methods unrelated with hyper link interface. So we don't need to change anything in interface declaration. Actually AT can get anchor accessible via hyper link interface and invoke its action or actions via action interface, therefore this shortcut (when action interface has special meaning for hyper link) is not necessary. Btw, Firefox implementation doesn't follow this part of spec which is wrong of course, at least for now.
Alex. On Fri, Oct 23, 2009 at 12:12 AM, Pete Brunet <[email protected]> wrote: > I agree with Jamie. However, I've not pushed for a change to this because, > at least for now, I think the churn would not be worth the effort. If > others disagree we can pursue this further. > > Pete > --- > James Teh wrote: > > On 21/10/2009 2:18 PM, Alexander Surkov wrote: > > > Are there areas that need improvement in either IA2 or ATK (or both)? > > > I didn't catch Jamie about hyperlink and action, partially I didn't > understand why hyperlink can have only one action if it's inherited > from hyperlink. I think I felt out of context. Jamie, please give > additional details. > > > I posted on this some time ago, but would need to go find the post. In > summary, at present, IAccessibleHyperlink inherits from > IAccessibleAction. IAccessibleAction::nActions (which is inherited) > returns the number of hyperlinks. Because of this, there can only be one > action for every hyperlink; i.e. action N must correspond to hyperlink > N. Imo, the relationship between IAHyperlink and IAAction is somewhat > confusing at best. > > Jamie > > > > _______________________________________________ > 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
