Issue metadata
Sign in to add a comment
|
Cannot minimize, maximize or close the Chrome window when using TouchInjection
Reported by
nidog...@gmail.com,
Nov 28
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0 Steps to reproduce the problem: 1. Open Chrome 2. Use the InjectTouchInput API to simulate a press on the close button 3. The window won't close What is the expected behavior? The control box should respond to input injection like any other window does. What went wrong? The minimize, maximize and close button correctly respond to mouse overs when using touch injection but it doesn't respond to presses Did this work before? Yes I don't know specifically, I know that it worked correctly a year ago but I don't have a more precise estimate Chrome version: 70.0.3538.110 Channel: stable OS Version: 10.0 Flash Version:
,
Nov 29
Thanks for filing the issue! Unable to reproduce the issue on reported chrome version 70.0.3538.110 using Windows 10 Surface Pro with the below mentioned steps. 1. Launched Chrome 2. Tried minimising, maximising and closing the Chrome window by normal touch input. We were able to minimise, maximise and close the window, without any issues. @Reporter: As we were not very sure about "InjectTouchInput API" could you please provide any further inputs on using this. It would also be helpful if shared with any test file.
,
Nov 30
It's an API provided by Microsoft to simulate touch input in Windows Docs: https://docs.microsoft.com/en-us/windows/desktop/api/winuser/nf-winuser-injecttouchinput Code Sample: https://code.msdn.microsoft.com/windowsdesktop/Touch-Injection-Sample-444d9bf7
,
Nov 30
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 3
As we do not have visual studio installed in test environment to check this as of now. Adding proper component for someone from the respective team for further investigation. @Reporter: If possible could you please attach a built sample to try a repro from our end. Thanks!
,
Dec 6
Hi, I've attached a small command-line executable that injects a touch at 700,200 on the desktop when you press enter. If you have a regular explorer window control box under "700,200", it will work as expected. If you place the Chrome window control box under that point, it will not work. It seems like the issue occurs when the contact point moves slightly between the down and up events; if I code the down and up at exactly the same pixel it works.
,
Dec 6
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 10
Tried checking the issue as per the test file provided in comment#6 on reported chrome version 70.0.3538.110 using Windows 10 1. Launched Chrome 2. Double clicked on TouchInjection.exe 3. In Command-line clicked Enter. We have observed everything seemed to work fine. Attaching the screen cast of the same for reference. @Reporter: As we are not sure about placing chrome window box under "700,200" point, Could you please provide a screencast explaining the issue. This would help us to triage it further in a better way. Thanks! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by viswa.karala@chromium.org
, Nov 28