JDK-4877530 : Unable to input text into JTextField in 1.4.1_02
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 1.4.1,1.4.1_02,1.4.2,1.4.2_01,5.0
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_8,windows_2000
  • CPU: x86,sparc
  • Submitted: 2003-06-11
  • Updated: 2004-03-08
  • Resolved: 2003-10-22
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availabitlity Release.

To download the current JDK release, click here.
Other
1.4.1_07 07Fixed
Related Reports
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
Relates :  
Relates :  
Relates :  
Description
We are unable to input text correctly into a JTextField after a javascript alert box is displayed.  The problem occurs when loading an applet on a Solaris 8 workstation with JRE 1.4.1_02 b6 and Netscape 7, rev 1.0.1.  The problem also reproduces on Solaris 9.  This appears to be a plugin/Netscape browser issue. The problem does not appear on a Windows machine running Netscape 7 and the 1.4.1_02 pluNetscagin.  Nor does the problem appear when the applet is loaded in Mozilla.  The problem appears to get triggered after the applet with the text field loses focus. 

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.4.1_07 tiger-beta FIXED IN: 1.4.1_07 tiger-beta INTEGRATED IN: 1.4.1_07 tiger-beta
2004-08-24

EVALUATION It appears to be focus related issue. After dismissing the alert box, focus does not return to the JTextField, even it still has blinking cursor. Also reproducible with 1.4.2 ###@###.### 2003-06-17 This does sound similar to other bugs we have seen. For example, 4806274. We think the root cause of the problem is that the plugin and the browser don't have a good protocol to communicate about focus ownership. It would be fine to reassign the bug to AWT. Thanks, Eric According to above comment from Eric, re-assign to AWT. ###@###.### 2003-06-24 Name: dmR10075 Date: 08/13/2003 This probably has been fixed by XEmbed. Will verify this after XEmbed work is integrated(18 August). ###@###.### 2003-08-13 ====================================================================== I'm going to move this to integrated since the other bugs that we expected the XEmbed work are gone. If the submitter could verify with Tiger build 30 or later, that would be great. ###@###.### 2003-12-09 This bug is fixed as 4878303 in 1.4.2_0xx ###@###.### 2004-03-08
2003-12-09