-
Bug
-
Resolution: Fixed
-
P4
-
6
-
b15
-
generic
-
linux
-
Verified
Launch the attached test on linux/solaris (SWT-GTK is required). The test creates an SWT top-level shell and adds three components to it: AWT text area, SWT text field and AWT text field. AWT components are laid to separate SWT_AWT composites (embedded frames).
The first problem is that in some cases no one of the components is focused when the window is shown. According to the XEmbed log, SWT shell first sends XEMBED_FOCUS_IN to the text area and then to the text field, so I expect the text field to be focused. However, only two cases are possible: focus is nowhere or focus is in the text area - both are wrong.
Then, when focus is initially in the text area, the second problem appears. If I click the text field with mouse, it doesn't get focused. But if I click the SWT text area first, then focus starts working properly.
The first problem is that in some cases no one of the components is focused when the window is shown. According to the XEmbed log, SWT shell first sends XEMBED_FOCUS_IN to the text area and then to the text field, so I expect the text field to be focused. However, only two cases are possible: focus is nowhere or focus is in the text area - both are wrong.
Then, when focus is initially in the text area, the second problem appears. If I click the text field with mouse, it doesn't get focused. But if I click the SWT text area first, then focus starts working properly.
- relates to
-
JDK-6469096 requestFocusXXX on unfocused window causes incorrect results under X
-
- Closed
-
-
JDK-6432035 Unable to edit content of JTextField intermittently following modal dialog
-
- Closed
-
-
JDK-6557375 Focus is lost when tabbing SWT_AWT to SWT to SWT_AWT
-
- Closed
-