We got a report from a customer that when testing a new Chromebook model (Lenovo ThinkPad Yoga 11E) with touch screen, they could not use the built-in touch pad with the HTML5 client. They could interact just fine with the web browser and the rest of the system. On a Chromebook without touch screen (HP Chromebook 11 G4), the touch pad worked just fine with the HTML5 client.
See https://github.com/kanaka/noVNC/pull/619 and https://github.com/kanaka/noVNC/issues/510
We now have a Chromebook (Lenovo ThinkPad Yoga 11e). Can reproduce the issue.
Fixed in upstream now.
The same issue exists for Microsoft Surface devices. It is a general issue that our HTML5 client for now only handles EITHER touch OR mouse, never both. This is fixed upstream. Also note that the control bar handle can't be moved using touch in IE and Edge on Microsoft Surface devices. This is also fixed upstream now.
So, to summarize; On devices such as Chromebooks and Microsoft Surfaces, which have both a mouse and a touch screen, there are a number of issues with mouse input in the HTML5 client. Issues found on a Microsoft Surface device using Windows 10: * Touch input doesn't work in IE or Edge * Mouse input doesn't work in Chrome * The new control bar handle can't be moved using touch on IE and Edge (Note that both mouse and touch works in Firefox.) Issue found on a Chromebook with a touch screen: * Mouse input doesn't work
Fixed now.
While touch + normal pointer events seems to work just fine now, there is a problem with touch input. I've seen this on the Yoga 11e Chromebook, in "tablet" mode (keyboard folded away). Steps to reproduce: 1. Start a session 2. Bring out keyboard to decrease screen size without resizing session 3. Grab the control bar and drag it up to reach the bottom half of the session 4. Click and drag the desktop to see touch events happen *not* beneath your fingers, but offset by approximately the amount you scrolled.
(In reply to comment #10) > While touch + normal pointer events seems to work just fine now, there is a > problem with touch input. > > I've seen this on the Yoga 11e Chromebook, in "tablet" mode (keyboard folded > away). > > Steps to reproduce: > 1. Start a session > > 2. Bring out keyboard to decrease screen size without resizing session > > 3. Grab the control bar and drag it up to reach the bottom half of the session > > 4. Click and drag the desktop to see touch events happen *not* beneath your > fingers, but offset by approximately the amount you scrolled. Not a regression can reproduce with ThinLinc 4.7.0. Can also reproduce on our Windows 10 tablet. Created bug 6163.
(In reply to comment #11) > Not a regression can reproduce with ThinLinc 4.7.0. Can also reproduce on our > Windows 10 tablet. Created bug 6163. In that case, closing. Both touch and mouse works at the same time on the Chromebook.
*** Bug 5516 has been marked as a duplicate of this bug. ***
