Bug 53961 - TabFolder doesn't cycle through conflicting mnemonics
Summary: TabFolder doesn't cycle through conflicting mnemonics
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.0   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-05 18:47 EST by Jared Burns CLA
Modified: 2004-03-11 18:10 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jared Burns CLA 2004-03-05 18:47:02 EST
The TabFolder doesn't handle conflicting mnemonics in a very friendly way. An example of this 
problem can be seen in Eclipse's launch configuration dialog.

1. Bring up the launch config dialog and select a Runtime-workbench configuration.
2. With the "Arguments" tab selected, observe that there are three mnemonics visible which apply 
to the letter 'c':
  a. The "&Classpath entries" field within the Arguments tab.
  b. The "&Configuration" tab.
  c. The "&Common" tab.
3. Press alt+c. The Configuration tab is given focus.
4. Press alt+c again. The Configuration tab retains focus.

When focus is up in the tab area, I would expect to cycle between tabs with conflicting mnemonics 
(the way they do in menus, preference pages, etc.). When focus is inside a tab, I would expect to 
cycle between widgets with conflicting mnemonics and then go to any "tab headers" with the 
same mnemonic when there are no more conflicts inside the tab.

So in the test case up above, if focus is inside the Arguments tab, I'd expect focus to first go the the 
"Classpath entries" widget, then up to the "Configuration" tab, and then to the "Common" tab. 
Once focus is in the "tab header" area, I'd expect focus to stay there until the user hits the TAB 
key to put focus inside the tab. tab.
Comment 1 Steve Northover CLA 2004-03-11 18:10:26 EST
This is platform specific behavior.  Sensible applications know what they are 
doing and don't define conflicts.  Frameworks however ...

Sorry WONTFIX.