JDK-4978234 : keyboard issue using suntea with Java 1.5 plugin and mozilla 1.6b
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 5.0
  • Priority: P2
  • Status: Closed
  • Resolution: Cannot Reproduce
  • OS: solaris_10
  • CPU: x86
  • Submitted: 2004-01-14
  • Updated: 2004-08-16
  • Resolved: 2004-08-16
Related Reports
Relates :  
Description
mattw@gerome]:~> uname -a
SunOS gerome 5.10 s10_50 i86pc i386 i86pc
[mattw@gerome]:~> java -fullversion
java full version "1.5.0-beta-b32"
[mattw@gerome]:~> mozilla -version
[mattw@gerome]:~> Mozilla 1.6b, Copyright (c) 2003 mozilla.org, build 2003121008

No keyboard entries are made when logging into suntea using the plugin in 
/usr/java/jre/plugin/i386/ns7 

When I switch to /usr/j2se/jre/plugin/i386/ns610 suntea works fine.

Here is the java console output
../gtk-2.0-key/gtkrc:6: Binding specification is unsupported, ignoring
../gtk-2.0-key/gtkrc:14: Binding specification is unsupported, ignoring
../gtk-2.0-key/gtkrc:16: Binding assignment is unsupported, ignoring
../gtk-2.0-key/gtkrc:17: Binding assignment is unsupported, ignoring
../gtk-2.0-key/gtkrc:18: Binding assignment is unsupported, ignoring
com.sun.java.swing.plaf.gtk.GTKLookAndFeel/icons/Inform.gif not found.
../gtk-2.0-key/gtkrc:6: Binding specification is unsupported, ignoring
../gtk-2.0-key/gtkrc:14: Binding specification is unsupported, ignoring
../gtk-2.0-key/gtkrc:16: Binding assignment is unsupported, ignoring
../gtk-2.0-key/gtkrc:17: Binding assignment is unsupported, ignoring
../gtk-2.0-key/gtkrc:18: Binding assignment is unsupported, ignoring
../gtk-2.0-key/gtkrc:6: Binding specification is unsupported, ignoring
../gtk-2.0-key/gtkrc:14: Binding specification is unsupported, ignoring
../gtk-2.0-key/gtkrc:16: Binding assignment is unsupported, ignoring
../gtk-2.0-key/gtkrc:17: Binding assignment is unsupported, ignoring
../gtk-2.0-key/gtkrc:18: Binding assignment is unsupported, ignoring
../gtk-2.0-key/gtkrc:6: Binding specification is unsupported, ignoring
../gtk-2.0-key/gtkrc:14: Binding specification is unsupported, ignoring
../gtk-2.0-key/gtkrc:16: Binding assignment is unsupported, ignoring
../gtk-2.0-key/gtkrc:17: Binding assignment is unsupported, ignoring
../gtk-2.0-key/gtkrc:18: Binding assignment is unsupported, ignoring

Comments
EVALUATION It's unclear exactly what the problem is here. What does it mean that "no keyboard entries are made"? Does it mean that the user cannot enter text into any component? The exact steps to reproduce this problem are needed. Please include details on how to setup Mozilla to use the version of plugin in question. Important to note is that the console warnings about "bindings" are not a problem and are irrelevant. This is simply a warning to the user that we don't support any custom key bindings defined in their RC file. This support may be added in the future (bug 4813953). These warnings have NOTHING to do with the user's ability to enter data into components. Another thought on this: There did seem to be a focus bug that was addressed recently. Could the submitter try this test again with the most recent promoted build to see if the problem still exists (not the warnings though, which WILL still be there). One other item of note in this bug is the warning about the missing icon image. It too would be unrelated to any keyboard issue. However it is something that may be worth looking into further (possibly as a separate low priority bug). ###@###.### 2004-01-21 I saw this bug reproduced and spoke to ###@###.### about his findings. Yes, "no keyboard entries are made" means that typing doesn't enter text into a text field when it should. This bug can be reproduced on Solaris 9 Sparc under GNOME 2.0 with tiger b35. He could not reproduce it on Linux. So this could be a MAWT vs. XAWT bug. I've attached an AWT-only test which also required unfocusing/refocusing a Frame before KeyEvents were generated. ###@###.### 2004-01-21 I wonder if this is related to 4972534? We need to fix this for tiger. ###@###.### 2004-01-21 Name: dmR10075 Date: 01/23/2004 4972534 is most likely a duplicate of this bug. Can't verify that since I don't have suntea. ###@###.### 2004-1-23 ====================================================================== I am not sure this is the same problem as 4972534. I tested the fix of 4972534 with suntea and the problem still exists. ###@###.### 2004-01-26 Name: rpR10076 Date: 02/26/2004 As reported by ###@###.###, the submitter no longer sees the bug. the problem is that the majority of AWT team doesn't have access to SunTea, it would be very difficult to look into it further even though we would like to understand what fixed it, if something did. The bug is marked as escalated, so I'll wait a couple of days and if I don't hear anything from escalation engineers, I'll close it out. ###@###.### ====================================================================== Name: rpR10076 Date: 03/02/2004 According to ###@###.###, the submitter can no longer reproduce this bug, and the bug can be closed. ###@###.### ======================================================================
17-08-2004

WORK AROUND ###@###.### 2004-01-14 Use 1.4.2 plugin
14-01-2004