After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 525316 - Orca does not always give the correct output when navigating the eclipse project explorer tree.
Orca does not always give the correct output when navigating the eclipse proj...
Status: RESOLVED NOTGNOME
Product: orca
Classification: Applications
Component: general
2.22.x
Other All
: Normal normal
: FUTURE
Assigned To: Orca Maintainers
Orca Maintainers
3.0?
Depends on:
Blocks: 575776
 
 
Reported: 2008-03-31 12:46 UTC by Michael Whapples
Modified: 2013-01-02 16:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Michael Whapples 2008-03-31 12:46:23 UTC
Please describe the problem:
When navigating through the project explorer tree of eclipse with an item at level 6 visible, orca will not produce the correct output below this item.

Steps to reproduce:
1. Open eclipse and create a new project.
2. Add a source directory, a package inside the source directory, and two classes containing methods. At this point it should be possible to get to tree level 6.
3. expand each item in the tree (second class does not need to be expanded). Cursor from the top of the tree and observe output.

Actual results:
Orca produces correct output until after the first class (after the first block of items at level 6). After this block of items at level 6, it gives the item just before the block at level 6 (the item at level 5 which they are children of).

Expected results:
The selected items name should be given as output.

Does this happen every time?
Seems to always happen.

Other information:
eclipse being used is version 3.3
Comment 1 Willie Walker 2009-02-18 21:55:25 UTC
Thanks Michael.  We don't develop or use eclipse, so it may take a long time for us to get this.  If you want to try to work on it, though, please do!  We're happy to review/commit patches.
Comment 2 Rui Batista 2010-04-04 23:13:02 UTC
Hi,

I can confirm this in eclipse 3.5.
Comment 3 Michael Whapples 2010-04-04 23:23:07 UTC
I wonder whether this is a specific eclipse bug or whether it may apply to other GTK applications (NOTE: eclipse uses SWT which uses platform specific controls, so on Linux GTK controls). I think I have observed similar elsewhere but can't think of one at the moment. Should I find one I will note it down, then I can tell whether its GTK, SWT, etc.
Comment 4 Jose Vilmar Estacio de Souza 2010-04-28 19:57:09 UTC
I can confirm in eclipse 3.6.
However I discovered that if I move to speak cell pressing OrcaKey+f11, the problem seems to disappear.
Comment 5 Joanmarie Diggs (IRC: joanie) 2010-04-28 20:31:32 UTC
Any noticeable differences in the accessible hierarchy between items not at level 6 and items at level 6?
Comment 6 Jose Vilmar Estacio de Souza 2010-04-28 21:17:32 UTC
(In reply to comment #5)
> Any noticeable differences in the accessible hierarchy between items not at
> level 6 and items at level 6?
I did not notice any difference.
Comment 7 Jose Vilmar Estacio de Souza 2010-05-29 14:50:11 UTC
Seems that problem happens when changing from level 4 to level 2, level 5 to level 3, level 6 to level 2 and etc.
No problems when changing from level 4 to level 3, level 5 to level 4, level 6 to level 5 and etc.
I didn't understand how to orca deal with  an OBJECT EVENT object:active-descendant-changed, raised when levels change.
Comment 8 Joanmarie Diggs (IRC: joanie) 2010-07-05 02:45:24 UTC
(3.0 Planning Spam-o-rama. Sorry!)
Comment 9 Jose Vilmar Estacio de Souza 2010-07-10 16:43:33 UTC
I opened the following bug in eclipse:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=319467

Please help  adding more information.
Comment 10 Joanmarie Diggs (IRC: joanie) 2013-01-02 16:03:45 UTC
Keeping Orca bugs open for things which are not Orca bugs makes it harder to identify what bugs we need to fix in Orca. An Eclipse bug has been opened for this issue, so I'm closing this original bug as NOTGNOME.