JDK-8198605 : Touch keyboard is shown for a non-focusable text component
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 8u172,10,11
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_10
  • Submitted: 2018-02-23
  • Updated: 2019-01-14
  • Resolved: 2018-03-05
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 Availability Release.

To download the current JDK release, click here.
JDK 11 JDK 7 JDK 8
11 b05Fixed 7u201Fixed 8u181Fixed
Related Reports
Relates :  
JDK-8166772 - Touch keyboard is not shown for text components on a screen touch
Description
Touch keyboard is shown for text component even when it is Non-Focusable

Reproducible on Microsoft Surface (Windows 10 Tablet Mode)

Steps to reproduce:
1.Run the attached "JTouchTest2.java" or "TouchTest2.java" with JDK 8u172 b06
2.Check the checkbox for Non-Focusable for any component
3.Click on the editable area of the  component 

Expected behavior : the on screen keyboard must not be shown
Actual behavior : the on screen keyboard is shown

Is it a regression: No, this is part of the new functionality introduced in 8u172 b01 as fix for JDK-8166772
Comments
The original test cases attached by the bug filer to the bug record were edited: - to address thread-safety; - to make the shown frames closable so that they did not block the application from exiting; - to make them independent on the attached "PrintQL_Procedures.html" file. The new versions of the test cases are the attached files: "JTouchTest2.java", "TouchTest2.java".
06-03-2018
Hello Victor, yes of course. The bug was reproduced on a PC with a touch screen and MS Windows 10 OS with JDK 10+44, JDK 8u172 b07. Confirm that this issue is a bug. During development of the fix for JDK-8166772 I thought that checking, if a component is focusable or non-focusable, would have been an extra check, however now it is seen that it is necessary to take into account this condition also. Starting to work on a fix for this bug.
26-02-2018
Changed "relates to" link to refer to the main bug JDK-8166772 instead of its backport, which was previously referred through this link.
26-02-2018
this is related to new feature introduced by Anton previously
23-02-2018
Anton, can you please look at this request?
23-02-2018