Bug 73485 - JAWS does not read TableCursor cells
Summary: JAWS does not read TableCursor cells
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-08 15:09 EDT by Ryan Manwiller CLA
Modified: 2021-11-12 11:34 EST (History)
1 user (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 Ryan Manwiller CLA 2004-09-08 15:09:04 EDT 
When clicking on, or tabbing to, the cells in a TableCursor 
(org.eclipse.swt.custom), JAWS doesn't read the cell contents.

Narrator reads the contents of the cell in the first column.

Using eclipse Version: 3.0.1
Build id: 200408250800
Comment 1 Carolyn MacLeod CLA 2010-09-07 12:14:23 EDT 
With JAWS 11 and Eclipse 3.6, the TableCursor snippet is read correctly:
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet96.java

It also works with Window-Eyes.

Are you doing something differently than in Snippet96?
Comment 2 Lefty A. Rivera-Correa CLA 2010-09-07 13:02:49 EDT 
I'm using Eclipse 3.4 and I can't move to Eclipse 3.6.Could the fix be ported to Eclipse 3.4?
Comment 3 Carolyn MacLeod CLA 2010-09-07 13:14:29 EDT 
I don't know what the fix is - it could be multiple things.
Can you try running Snippet96 on your Eclipse 3.4 (it says how at the top of the SWT snippets page: http://www.eclipse.org/swt/snippets/). If that works, then maybe you can see what you are doing differently.
Comment 4 Lefty A. Rivera-Correa CLA 2010-09-07 15:02:47 EDT 
The snippet works on 3.6 but it doesn't on 3.4
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:11:36 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.