Bug 7398 - IE and Edge does not have touch event support
Summary: IE and Edge does not have touch event support
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Access (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.14.0
Assignee: Frida Flodin
Depends on: 7550
  Show dependency treegraph
Reported: 2019-10-11 13:36 CEST by Niko Lehto
Modified: 2021-11-18 15:48 CET (History)
3 users (show)

See Also:
Acceptance Criteria:


Description Niko Lehto cendio 2019-10-11 13:36:24 CEST
In both browsers we detect touch and display the touch specific control bar, but no touch events are fired.

Edge does not support touch events by default. Enabling this can be done in the developer settings accessed by writing "about:flags" in the URL.

IE does not support touch events at all. 

Some problems caused by this:

Causes our "Active mouse button" to not work.

In IE the cursor disappears after a touch because a mouseleave event is sent instead on touchend.

The cursor also disappears on Edge when touch event support is disabled but it might be related to upstream bug:

Se also bug 5779
Comment 1 Pierre Ossman cendio 2019-10-16 09:19:13 CEST
Both IE and Edge claim to support PointerEvent. Perhaps touch works better with that?

Also see bug 7395.
Comment 2 Samuel Mannehed cendio 2021-11-17 13:27:25 CET
As of bug 7550 we are dropping support for IE, which means that the IE part of this bug no longer is relevant.

Edge has been rewritten and is now based on Chrome, so the issues there might have been solved. Testing of this still needs to be done before closing the bug.
Comment 3 William Sjöblom cendio 2021-11-17 13:54:12 CET
Once IE support is removed from webaccess, we are free to remove all traces of nodejs along with all nodejs packages from cenbuild. Previously, nodejs et al. were used exclusively to provide polyfills for IE.
Comment 4 Frida Flodin cendio 2021-11-18 15:48:58 CET
I could reproduce the issue in IE on Windows 10. But since we drop support for IE we will not fix this. 

However, the issue is gone in new Edge. Tested with:

* tl-4.12.1 server on Ubuntu 20.04
* Edge Version 95.0.1020.53 on Windows 10

Note You need to log in before you can comment on or make changes to this bug.