Name: gm110360 Date: 04/23/2002


FULL PRODUCT VERSION :
java version "1.4.0-rc"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-rc-b91)
Java HotSpot(TM) Client VM (build 1.4.0-rc-b91, mixed mode)


FULL OPERATING SYSTEM VERSION : Windows NT Version 4.0


A DESCRIPTION OF THE PROBLEM :
Combo box does not behave in 1.4 the same it used to in 1.3
when “windows look and feel” is used.

If Up or Down arrows are used with combo box, the selected
item should change to the next/prev item in the list (and
it worked correctly in 1.3).

If Down arrow is pressed with 1.4 java, a pull-down list
opens. When Up arrow is pressed with 1.4 java, nothing
happens.

REGRESSION. Last worked in version 1.3.1

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Display a Frame with a combo box that has
items "A", "B", "C"
2. Focus a combo box and select an item "B"
3. Press Up and observe that nothing happened
4. Press Down arrow and observe that pull - down list got
opened

EXPECTED VERSUS ACTUAL BEHAVIOR :
I expected selection to swith to the next item in the list
when arrow keys are used

This bug can be reproduced always.

---------- BEGIN SOURCE ----------
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
import java.util.*;

public class ComboBoxTest
{
  public static void main(String[] args)
  {
    try
    {
      UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName());
    }
    catch (Exception exc)
    {
    }

    ComboBoxTest comboBoxTest1 = new ComboBoxTest();

    Vector v = new Vector();
    v.add("A");
    v.add("B");
    v.add("C");

    JComboBox cb = new JComboBox(v);

    JFrame frame = new JFrame();
    frame.getContentPane().setLayout(new FlowLayout());

    frame.getContentPane().add(cb);

    frame.addWindowListener(new WindowAdapter()
    {
      public void windowClosing(WindowEvent e)
      {
        System.exit(0);
      }
    });

    frame.setBounds(100, 100, 300, 70);
    frame.setVisible(true);
  }
}
---------- END SOURCE ----------

Release Regression From : 1.3.1_03
The above release value was the last known release where this
bug was known to work. Since then there has been a regression.

(Review ID: 139673)
======================================================================