Closed Bug 414976 Opened 17 years ago Closed 16 years ago

Support RELATION_NODE_CHILD_OF for ARIA tree views

Categories

(Core :: Disability Access APIs, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: aaronlev, Assigned: aaronlev)

References

(Blocks 1 open bug)

Details

(Keywords: access)

Attachments

(2 files, 2 obsolete files)

Each tree item should use this relation to point to the parent tree item.
Attached patch Works! (obsolete) — Splinter Review
Attachment #300508 - Attachment is obsolete: true
Attachment #300574 - Flags: review?(surkov.alexander)
Testcase #2 is a tree using role="group" to organize the levels:
http://www.mozilla.org/access/dhtml/tree 

Testcase #3 is the bookmarks tree in the side panel

All 3 now support node_child_of

This bug will allow screen readers on Windows to announce the ancestry of a given tree item.
Comment on attachment 300574 [details] [diff] [review]
Works!


>+
>+  // Possibly a tree arranged by using role="group" to organize levels
>+  // In this case the parent of the tree item will be a group and the
>+  // previous sibling of that should be the tree item parent.
>+  // Or, if the parent is something other than a tree we will return that.

could you upload testcases for these?

>+  nsCOMPtr<nsIAccessible> prevAccessible;
>+  parentAccessible->GetPreviousSibling(getter_AddRefs(prevAccessible));
>+  if (!prevAccessible)
>+    return;
>+  prevAccessible->GetFinalRole(&role);
>+  if (role != nsIAccessibleRole::ROLE_OUTLINEITEM) {
>+    nsCOMPtr<nsIAccessible> tempAccessible = prevAccessible;
>+    tempAccessible->GetPreviousSibling(getter_AddRefs(prevAccessible));
>+    if (!prevAccessible)
>+      return;
>+    prevAccessible->GetFinalRole(&role);
>+  }

I didn't get why you try to get previous + previous siblings?

> 
>   //currentlly only for ATK. and in the future, we'll sync MSAA and ATK same. 
>   //that's why ATK specific code shows here

please remove this too.
For the group structure testcase, see comment 5 :b

> I didn't get why you try to get previous + previous siblings?
Sometimes there's an extra text accessible in between. Maybe we should look into why, I suppose.


(In reply to comment #7)
> > I didn't get why you try to get previous + previous siblings?
> Sometimes there's an extra text accessible in between. Maybe we should look
> into why, I suppose.
> 

Are there more strong rules? Otherwise what if someone will want to put one more accessible?
Attachment #300633 - Flags: review?(surkov.alexander)
Attachment #300574 - Attachment is obsolete: true
Attachment #300574 - Flags: review?(surkov.alexander)
Comment on attachment 300633 [details] [diff] [review]
Fix Surkov's nits

looks ok
Attachment #300633 - Flags: review?(surkov.alexander) → review+
Attachment #300633 - Flags: approval1.9?
Attachment #300633 - Flags: approval1.9? → approval1.9+
checked in
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
in-testsuite?
Flags: in-testsuite?
mochitests have been added in bug 502164
Flags: in-testsuite? → in-testsuite+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: