JDK-4362411 : JTextField does not accept some numeric keys on Linux
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 1.3.0
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux
  • CPU: x86
  • Submitted: 2000-08-14
  • Updated: 2001-02-18
  • Resolved: 2001-02-18
Related Reports
Duplicate :  
Description

Name: skT45625			Date: 08/14/2000


java version "1.3.0beta_refresh"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0beta_refresh-b09)
Java HotSpot(TM) Client VM (build 1.3.0beta-b07, mixed mode)


There is a bug with JTextField under Linux (JDK1.3 refreshed beta).
Given the following sample application:

import java.awt.*;
import javax.swing.*;

public class TextTest extends JFrame
{
	// Application main entry point:
	public static void main(String[] args)
	{
		TextTest	win = new TextTest();
	}
	// Constructor of the frame
	private TextTest()
	{
		super("JTextField Test");
		Container	contentPane = getContentPane();
		contentPane.setLayout(new BorderLayout());
		JTextField	field = new JTextField(20);
		contentPane.add(field, BorderLayout.CENTER);
		setDefaultCloseOperation(EXIT_ON_CLOSE);
		pack();
		setVisible(true);
	}
};

I tried to enter numeric value (without using the numeric keypad) in the
JTextField.
Only 4 and 6 are accepted ! 1,2,3,5,7,8,9 and 0 are rejected !
As I could only check this on one computer, here is the description of it
(since maybe this bug could depend on the material):
	Gateway 2000 Solo 2500
	French Keyboard (AZERTY)

I tried the same application under Windows NT and it worked fine.
(Review ID: 108398) 
======================================================================

Comments
WORK AROUND Name: skT45625 Date: 08/14/2000 The only workaround I found until now is to use the emulated numeric keypad on the Solo Notebook to enter numeric keys. This workaround can be used for testing purposes, but of course it might not be used by end-users whom I don't want to impose the way to enter numeric values. ======================================================================
11-06-2004

EVALUATION Not reproducible in Build 15. mike.bronson@eng 2000-08-15 Probably a duplicate of 4371923. eric.hawkes@eng 2001-02-16 Apparently, at least one person found it confusing that this bug was closed as not reproducible in a release after 1.3 (see 4381329). Perhaps it would be clearer if I closed it as a duplicate of the bug that fixed the problem: 4371923. eric.hawkes@eng 2001-02-17
17-02-2001