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

Bug 311646

Summary: [Accessibility] Composite subclasses with Accessibles aren't appearing in Accessibility Inspector
Product: [Eclipse Project] Platform Reporter: Scott Kovatch <skovatch>
Component: SWTAssignee: Scott Kovatch <skovatch>
Status: RESOLVED INVALID QA Contact: Carolyn MacLeod <carolynmacleod4>
Severity: normal    
Priority: P3 CC: platform-swt-inbox, skovatch
Version: 3.6   
Target Milestone: ---   
Hardware: Macintosh   
OS: Mac OS X   
Whiteboard:
Attachments:
Description Flags
Fix
none
Fix none

Description Scott Kovatch CLA 2010-05-04 20:40:02 EDT 
I20100429-1549

Composites that have had getAccessible() called on them don't appear in Accessibility Inspector.

1. Launch Accessibility Inspector
2. Run AccessibleRelationsExample.
3. Mouse over the list on the right side of the window.
4. Look at the inspector window.

"<AXOutline>" should appear below <AXScrollArea>. Instead, it goes directly to AXRow.
Comment 1 Scott Kovatch CLA 2010-05-05 19:13:24 EDT 
This is because my test for whether or not an Accessible should be ignored is flawed. If there are no AccessibleControlListeners that could change the role, then the default visibility shouldn't change.
Comment 2 Scott Kovatch CLA 2010-05-05 20:05:55 EDT 
Created attachment 167249 [details]
Fix

If there are no listeners to override the role, the widget should not be ignored by accessibility.
Comment 3 Scott Kovatch CLA 2010-05-05 20:08:23 EDT 
Created attachment 167250 [details]
Fix

Patch for just this problem.
Comment 4 Carolyn MacLeod CLA 2010-05-06 11:38:26 EDT 
I actually don't see any difference, before or after the patch. In both cases, I get:
<AXApplication: “java”>
 <AXWindow: “Accessible Relations”>
  <AXScrollArea>
   <AXTable>
    <AXRow: “[Bananas]”>
     <AXTextField: “Bananas”>

Not sure what I am doing differently from you. I am running AccessibleRelationsExample from the branch.

(If you do use the patch as part of the fix, you might want to reuse listenerCount in the for loop).
Comment 5 Scott Kovatch CLA 2010-05-06 17:38:49 EDT 
Hmm... In a clean workspace I can't reproduce this either. I had some other changes in progress related to CCombo accessibility, so it's possible those were breaking this change.

I'll mark this invalid and we'll pretend it never happened. :-)
Comment 6 Carolyn MacLeod CLA 2010-05-06 17:42:27 EDT 
+1  :)