Java Solaris Communities Sun Store Join SDN My Profile Why Join?
 
Bug Database
Bug Detail
Quick Lists
Top 25 Bugs
Top 25 RFE's
Recently Closed Bugs
Printable Page Printable Page


Bug Database
Bug ID: 4070691
Votes 0
Synopsis Solaris and win32 differ in the way windowActivated() gets called (focus issue)
Category java:classes_awt
Reported Against 1.1.4
Release Fixed
State 11-Closed, duplicate of 4369903, bug
Priority: 4-Low
Related Bugs 4369903
Submit Date 08-AUG-1997
Description
On win32, a setVisible() call causes a windowActivated() method to be called if the frame is registered as a windowListener. While on Solaris, windowActivated() is called only when the frame gains focus.

In HJ, the frame is registered as a listener for Window events and when windowActivated() is called, we want to set focus to the type-in textfield.
On windows, this caused severe problems when the frame was cloned and we moved focus back to the original frame. Both frames would continuously vie for focus locking up the browser windows. THis was beacuse on win32, a setVisible() call (which was made when the clone frame is created) turns around and calls windowActivated(). On solaris, windowActivated() was called only when the frame
received focus which seems like the correct thing to do.
Work Around
N/A
Evaluation
Looks like a focus issue
  xxxxx@xxxxx   2000-09-19

i think this is duplicate of 4369903 (Focus on window activation does
not work correctly).  Fix already integrated, also we have workaround:
application should use requestFocusInWindow() instead requestFocus().
  xxxxx@xxxxx   2001-4-17
Comments
  
  Include a link with my name & email   


PLEASE NOTE: JDK6 is formerly known as Project Mustang