Bug 322396 - [JFace] Orca sometimes cannot read Eclipse status line
Summary: [JFace] Orca sometimes cannot read Eclipse status line
Status: CLOSED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: accessibility, needinfo
: 530632 (view as bug list)
Depends on: 270472
Blocks:
  Show dependency tree
 
Reported: 2010-08-11 11:37 EDT by Oleg Besedin CLA
Modified: 2019-02-14 14:22 EST (History)
10 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Oleg Besedin CLA 2010-08-11 11:37:53 EDT 
+++ This bug was initially created as a clone of Bug #270472 +++

From bug 78244:

> > I am testing eclipse with orca, but with orca I can not read the status line
> 
> Does Orca read the status line in any other GTK application? If so, what Orca
> command do you use to read a status line?
Yes, I can read the status line in applications like gnome-terminal,
thunderbird, firefox, evolution, open office and etc. I mapped
Kps_lock+pageDown (or Insert+PageDown) to read the status line, like in jaws.
Comment 1 Oleg Besedin CLA 2010-08-11 11:53:19 EDT 
Patch from the bug 270472 applied to CVS Head.
Comment 2 jose vilmar estacio de souza CLA 2010-08-11 13:31:31 EDT 
(In reply to comment #1)
> Patch from the bug 270472 applied to CVS Head.

I can test if it is applied in nightly build.
Thanks.
Comment 3 Dani Megert CLA 2010-08-12 02:01:20 EDT 
>I can test if it is applied in nightly build.
The nightly builds take the source from HEAD i.e. if the comment says "applied to HEAD", then it means it will automatically be in the next nightly build.
Comment 4 jose vilmar estacio de souza CLA 2010-08-14 06:28:55 EDT 
Testing with Build id N20100813-2000, I found the following behavior:
1. When eclipse is launched and it presents a class in the editor, the status bar is shown. Orca reads the line and the column number, error/warnning messages and etc.
2. If i switch to package explorer and switch back to editor, orca no longer reads the content of the status bar.
Comment 5 Carolyn MacLeod CLA 2010-08-17 11:57:58 EDT 
According to Silenio in bug 270472 comment 11, if you give focus to the Outline view after this, then Orca+PageDown will work again. We should apply the patch for 3.6.1 (because it goes a long way towards fixing the problem), and close the 3.6.1 bug, then reopen this one with a new title: "Orca sometimes cannot read Eclipse status line". See comment 4 and bug 270472 comment 11 for details.
Comment 6 Oleg Besedin CLA 2010-08-17 14:09:35 EDT 
(In reply to comment #5)
> We should apply the patch
> for 3.6.1 (because it goes a long way towards fixing the problem), and close
> the 3.6.1 bug, then reopen this one with a new title: "Orca sometimes cannot
> read Eclipse status line".

This sounds like a good plan; done.
Comment 7 Oleg Besedin CLA 2011-02-03 09:49:55 EST 
Jose, Joan - any suggestions on what can we do on the Eclipse side to help?
Comment 8 jose vilmar estacio de souza CLA 2011-02-10 07:23:49 EST 
(In reply to comment #7)
> Jose, Joan - any suggestions on what can we do on the Eclipse side to help?

No suggestions. I'll install 3.7m5 to check if the problem is present.
Comment 9 Oleg Besedin CLA 2011-04-25 09:47:07 EDT 
Removing 3.7 target milestone as we are at the end of the last development milestone and we need information from Orca.
Comment 10 Eric Williams CLA 2017-11-29 14:56:49 EST 
I'm trying to reproduce this issue but I'm a bit confused as to the steps, and there are multiple bugs linked. Can someone clarify? 

Also what is the default mapping for Orca to read the status line? I can't seem to find it.
Comment 11 Eric Williams CLA 2019-02-14 12:02:21 EST 
*** Bug 530632 has been marked as a duplicate of this bug. ***
Comment 12 Eric Williams CLA 2019-02-14 14:22:07 EST 
Seems the issue is no longer reproducible on 4.10, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=530632#c5