Bug 60876 - Accessibility: Run/Config dialog Debugger Options group not read
Summary: Accessibility: Run/Config dialog Debugger Options group not read
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-04 09:40 EDT by Tanya Wolff CLA
Modified: 2020-09-04 15:24 EDT (History)
2 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 Tanya Wolff CLA 2004-05-04 09:40:32 EDT 
Open the run/debug... configuration dialog and select a C/C++ Local 
application. Select the Debugger tab. Select either cygwin gdb debugger or GDB 
Debugger from the combolist dropdown. Open MS Inspect Objects. Tab or hover the 
mouse over the GDB Debugger input field, or the Main tab instide debugger 
Options. One of these should have "Debugger Options" as the first 'ancestor' in 
MS Inspect Objects. This will enable JAWS to read the group name before the 
control name. Currently, "Debugger options" appears after many "none" ancestors 
in the list, so it won't get read.
Comment 1 Alain Magloire CLA 2004-05-04 10:26:55 EDT 
Tanya this is the wrong category, please redirect you PR
to the debug/ui owner.  I do not even think that Mikhail
is on the cdt-core-inbox mailing list.
Comment 2 David Daoust CLA 2004-08-16 17:22:49 EDT 
deferred to 2.1 as per request by Tanya.
Comment 3 Nobody - feel free to take it CLA 2005-06-28 11:28:56 EDT 
Deferred.
Comment 4 Chris Recoskie CLA 2007-05-11 14:35:19 EDT 
Vivian please take a look.
Comment 5 Jonah Graham CLA 2019-12-30 18:55:25 EST 
This bug was assigned and targeted at a now released milestone (or Future or Next that isn't being used by CDT). As that milestone has now passed, the milestone field has been cleared. If this bug has been fixed, please set the milestone to the version it was fixed in and mark the bug as resolved.