Please describe the problem:
I have a GUI app with a tree view.  I run my accessibility logging app and am looking at the focus: event.  I have 4 rows and 3 columns in the tree.  When the tree does not have focus and I click on a cell in the middle column, the at-spi interface is incorrectly reporting which table cell contained the mouse click, it is one row too low.

Steps to reproduce:
1. click a button in my app -- make the button have focus.
2. click the top row in column 2 (focus handler reports 2nd-from-top was clicked)
3. click the button
4. click the 2nd-from-top in column 2 (focus reports 3rd-from-top)
5. click the button
6. click the 3rd-from-top in column 2 (focus reports 4th-from-top item, which is bottommost)
7. click the button
8. click the bottom column entry, an error is reported in the window where I launched my logging app:

** (gtk_hello:6438): WARNING **: gail_tree_view_ref_accessible_at_point: gtk_tree_view_get_path_at_pos () failed



Actual results:
See comments in parentheses above.

Expected results:
When I click on a particular row in an column, I expect that row to be reported as the focus

Does this happen every time?
Yes.

Other information:
My logging app uses AccessibleComponent_getAccessibleAtPoint() to drill down to the innermost Accessible* containing the mouse coordinates that cause the focus listener to be called.  Once I have the innermost Accessible, I retrieve its name and roleName.  roleName is "table cell".  The name is the text in that table cell.  I compare the name with what I clicked and can see it is off-by-1.