cannot click on Chrome elements when remoting from Android to Windows 10 using Mouse Mode |
|||||||
Issue descriptionVersion: 52.0.2743.10 OS: Android/Win10 What steps will reproduce the problem? (1)Connect to a Windows 10 host from Android (2)click the icon at the top to go from trackball to mouse mode (3)Open a Chrome Window and attempt to click or select anywhere within Chrome You see a brief impact animation but nothing happens You can click elsewhere within the session. Could not repro with a Windows 7 machine. This is not a regression.
,
May 31 2016
Was this using Me2Me or It2Me? If you try to use the touch interface locally on the Windows machine, can you interact with Chrome?
,
Jun 1 2016
This only occurs with an Android client, so its Me2Me. Locally there are no issues interacting with Chrome.
,
Jun 7 2016
this is interesting. On the touchscreen device, the bug does not occur at all. Mouse mode works perfectly, as does interacting locally with chrome. This issue only occurs on non-touchscreen devices.
,
Jun 7 2016
Do you mean that if the Windows host does not have a touchscreen, then Chrome does not respond to touch events injected by Chromoting host, but other applications do?
,
Jun 8 2016
Yes, exactly. More specifically, maximize and minimize work, but anything within chrome including graphics, links, the account switcher etc do not respond if the windows host does not have a touchscreen.
,
Jun 8 2016
Accepting touch input on non-touch-capable hardware is definitely a corner case, but since the OS is still capable of generating touch events (and most apps do the right thing) then we should at least make sure that the relevant folks have made a conscious decision not to support this mode.
,
Jun 14 2016
,
Aug 24 2016
Looks like Chrome will start accepting touch input from Android client if you manually turn on the tablet mode in control panel. Not sure why it doesn't take touch input in desktop mode.
,
May 30 2017
issue no longer occurs. closing |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ajnolley@chromium.org
, May 27 2016