Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 311997

Summary: Using Orca I can not know the number of line I'm editing.
Product: [Eclipse Project] Platform Reporter: jose vilmar estacio de souza <vilmar>
Component: TextAssignee: Platform-Text-Inbox <platform-text-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: daniel_megert, markus.kell.r, Silenio_Quarti
Version: 3.6   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description jose vilmar estacio de souza CLA 2010-05-06 22:15:30 EDT
With orca I can not know the number of the line that has focus in the editor.
One place where the line number can be find is the statusline but orca don't let me access the statusline.
Comment 1 Carolyn MacLeod CLA 2010-05-17 02:25:54 EDT
Moving this bug to Eclipse UI.

When the user types Ctrl+L in an Eclipse editor, the "Go To Line" dialog opens. The user can then type a line number in the text field, and select OK to go to that line.

Currently, the text field is unpopulated. If the text field instead contained the line number at the current cursor (i.e. the same line number that is displayed in the status line), and it it was selected, so that a new number could be typed over it, then a screen reader would speak the current line number from this text field. So a screen reader user who wanted to know the current line number would be able to press Ctrl+L and then Esc.

Note that bug 270472 discusses the issue of Orca not being able to read the status line.
Comment 2 Markus Keller CLA 2010-05-17 08:48:15 EDT
(In reply to comment #1)
That's bug 236241.
Comment 3 Dani Megert CLA 2010-05-17 10:49:51 EDT
As you can see in bug 223806 there exist other ideas on how to initialize that dialog but given the benefit we can get for blind users I'm inclined to change my mind and fix bug 236241 and close bug 223806 as WONTFIX. Also, I don't want to start storing the last line number per file.

*** This bug has been marked as a duplicate of bug 236241 ***