Bug 230485 - [Accessibility] Leopard: CTabFolder chevron does not work
Summary: [Accessibility] Leopard: CTabFolder chevron does not work
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.4   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: 3.6   Edit
Assignee: Carolyn MacLeod CLA
QA Contact: Scott Kovatch CLA
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2008-05-06 17:23 EDT by Duong Nguyen CLA
Modified: 2010-07-29 19:00 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Duong Nguyen CLA 2008-05-06 17:23:50 EDT
The chevron in a CTabFolder does not work properly when it is selected. When selected, a pop-up  list appears but the user cannot type or use the cursor key to selected the items in the list.

STEPS:
  - open a few editors
  - resize the sash until only one editor is visible and the chevron appears
  - select the editor Tab and press the Ctrl-tab until the editor tab is selected
  - press the right arrow key until the chevron has focus which will pop up a window

VoiceOver will say, "Voice over On" - which is odd but then you cannot navigate and select the items that is in the pop up list of opened editors.

Workaround:
   - use VoiceOver special keys to navigate to the list
   - OR press Tab a few times until the list gets focus
Comment 1 Scott Kovatch CLA 2010-07-28 18:14:15 EDT
This is still true in Cocoa. Control-option-space should select the chevron, but it doesn't.
Comment 2 Scott Kovatch CLA 2010-07-29 19:00:11 EDT
I stand corrected: control-shift-option-space clicks a button under the VoiceOver cursor.

Using the steps described I can't reproduce the problem. Ctrl-tab gets me up to the CTabFolder items, and then right-arrow eventually selects the chevron. I can then use up/down arrow to select the items in the popup list. I also have no problems typing in the text field.

Note that this is in Cocoa. I'm not planning to address this in Carbon, assuming it's still an issue there.