Mnemonics on JTabbedPane only work if IN one of the panes?

Question

I've run into an interesting behaivor on JTabbedPane. You can SEE the mnemonic for a tab pane, but unless your focus is on a control that's a child of one of the tabs in the JTabbedPane, you will will NOT be able to get a non-visible tab to display. It would seem (IMHO) that those nmemonics should work just like any other nmemonics in the dialog. If you type ALT-B you should go to the ALT-B Tab. See below for an example of this behavior. When in Label 1's field try out ALT-F and ALT-S (the two tab nmemnoics), nothing happens. When in Label 3's field you can ALT-F and ALT-S and have the dialog update as would be expected.
- james
public class TestMain
     public static void main(String[] args)
JPanel panel1 = newLabelAndFieldPanel( "Label 1", KeyEvent.VK_L, 0 );
JPanel panel2 = newLabelAndFieldPanel( "Label 2", KeyEvent.VK_A, 1 );
JPanel panel3 = newLabelAndFieldPanel( "Label 3", KeyEvent.VK_B, 2 );
JPanel panel4 = newLabelAndFieldPanel( "Label 4", KeyEvent.VK_E, 3 );
JTabbedPane tabPane = new JTabbedPane();
tabPane.addTab( "First Tab", panel3 );
tabPane.setMnemonicAt( 0, KeyEvent.VK_F );
tabPane.setDisplayedMnemonicIndexAt( 0, 0 );
tabPane.addTab( "Second Tab", panel4 );
tabPane.setMnemonicAt( 1, KeyEvent.VK_S );
tabPane.setDisplayedMnemonicIndexAt( 1, 0 );
JFrame frame = new JFrame( "Testing Mnemonics and JTabbedPane" );
frame.setSize( new Dimension( 500, 300 ) );
frame.getContentPane().setLayout(new GridLayout(0,1));
frame.getContentPane().add( panel1 );
frame.getContentPane().add( panel2 );
frame.getContentPane().add( tabPane );
frame.show();
     static JPanel newLabelAndFieldPanel( String labelText, int key, int pos )
JPanel panel = new JPanel(new GridLayout(1,0));
JLabel label = new JLabel( labelText );
JTextField field = new JTextField();
label.setLabelFor(field);
label.setDisplayedMnemonic( key );
label.setDisplayedMnemonicIndex( pos );
panel.add( label );
panel.add( field );
return panel;
}

Answer 1

This is the bug 4624207(http://developer.java.sun.com/developer/bugParade/bugs/4624207.html)
and it was fixed in 1.5