JDK-6224941 : REG: Unable to select the text from TextArea, TextField when they are non-focusable
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 5.0
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: generic
  • CPU: generic
  • Submitted: 2005-02-03
  • Updated: 2015-11-16
Related Reports
Relates :  
JDK-6469163 - java.awt.TextArea select(int,int) and insert(String,int) appear to not work
Relates :  
JDK-4095946 - 592677:TEXTFIELD TAB SELECTION CONFUSING; REMOVE ES_NOHIDESEL STYLE IN
Description
I have a frame with a TextArea and a TextField, each of them having some text in it. Both the text comps are non-focusable. Now when I try to select the text using mouse, the text is not getting selected. This is reproducible since Tiger on Win32 as well as Solaris / Linux with XToolkit. Not reproducible on Motif. Not reproducible on 1.4.2.  Non-Focusability should not prevent any mouse operations from happening on the component. Text must be selectable even when the component is non-focusable. 

I have attached a sample test. Execute the sample test. You would see a frame with a TextField and a TextArea. Try selecting the text shown in the above components. If you are unable to select, the bug is reproduced.
###@###.### 2005-2-03 06:26:53 GMT
Comments
EVALUATION A regression introduced in Tiger between b04 and b08. ###@###.### 2005-2-03 09:13:43 GMT On Windows, this one is (AGAIN) the result of ES_NOHIDESEL removal (see 4095946). In fact, you CAN select text in the TextArea/TextField when it is non-focusable. However, as ES_NOHIDESEL has been removed, the selection is invisible. There is NO way to fix this on Windows unless we revert to a native-uncompatible motif-compatible behavior with ES_NOHIDESEL. ###@###.### 2005-03-22 19:33:02 GMT Should finally decide what to do about this one. Now it seems to be too late for backing out 4095946 fix for Mustang. Committing to dolphin. ###@###.### 2005-06-27 13:01:53 GMT
03-02-2005