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

Bug 333501

Summary: SWT is missing the implementation of "Unavailable" state and other OS states of objects
Product: [Eclipse Project] Platform Reporter: Samer <selhelou>
Component: SWTAssignee: Platform-SWT-Inbox <platform-swt-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: carolynmacleod4, eclipse.felipe, selhelou, Silenio_Quarti, thatnitind
Version: 4.1Keywords: accessibility
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Samer CLA 2011-01-04 13:23:22 EST 
Build Identifier: 20100218-1602

There is no way to mark an object in SWT as Unavailable as their OS state. I checked the COM class that is included in SWT, and the unavailable state is commented. So in return, every object which appears to be unavailable actually will have the state of Normal on the OS level.
Please Advise.

Reproducible: Always
Comment 1 Samer CLA 2011-01-04 13:32:26 EST 
For additional information, I want the screen reader to mention that an object in unavailable in case it can't be clicked. As I experienced from other applications, the screen reader should say Unavailable if the State of the widget is Unavailable. Right now, I can't implement this feature without SWT implementing the Unavailable OS state.
Comment 2 Eclipse Genie CLA 2020-06-08 13:41:41 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.