www.cendio.com
Bug 7395 - Touch is not working on Firefox and Chrome
: Touch is not working on Firefox and Chrome
Status: NEW
: ThinLinc
Web Access
: trunk
: PC Unknown
: P2 Normal
: MediumPrio
Assigned To:
:
:
:
: 6348 7396
  Show dependency treegraph
 
Reported: 2019-10-09 16:41 by
Modified: 2019-10-21 14:45 (History)
Acceptance Criteria:


Attachments


Note

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


Description From cendio 2019-10-09 16:41:10
Firefox has stopped showing the touch buttons when running on a Windows system
with touch support. Tested with Firefox 69 on our Windows 10 laptop.

It must have worked at some point as bug 6348 had issues with the keyboard
button with Firefox on Windows.

Also note bug 5882 which had the same issue but for Edge.
------- Comment #1 From cendio 2019-10-09 16:44:37 -------
Check bug 6348 after fixing this as it can most likely be closed.
------- Comment #2 From cendio 2019-10-10 12:48:14 -------
Firefox apparently had problems last time upstream changed the touch detection:

https://github.com/novnc/noVNC/pull/650

Might have been an issue for a long time.
------- Comment #3 From cendio 2019-10-10 14:22:49 -------
Touch support completely disabled. Seems to be a bug in Firefox as older
versions work. Latest working is Firefox 66. Filed a bug upstream: 

https://bugzilla.mozilla.org/show_bug.cgi?id=1587760
------- Comment #4 From cendio 2019-10-16 09:17:30 -------
So upstream has gotten back to us with the fact that this is intentional.
Apparently they see a huge problem with sites assuming that touch means mobile
and make the site difficult to use on a desktop machine.

Their solution is to surrender the TouchEvent API to the mobile only domain,
and sites that want touch on desktop need to use the newer PointerEvent API. So
I guess we'll have to have a look at that. Most browsers support it (even IE!),
but unfortunately Safari only does in the latest version. So we probably need
to keep some backwards compatibility.

They also claim that Chrome and Edge will also follow this behaviour. Safari is
unknown, but touch on macOS doesn't seem to be a big thing anyway.
------- Comment #5 From cendio 2019-10-16 09:20:06 -------
Upstream also claims that we can get the old behaviour back by setting:

dom.w3c_touch_events.enabled = 1
dom.w3c_touch_events.legacy_apis.enabled = true
------- Comment #6 From cendio 2019-10-21 14:45:32 -------
(In reply to comment #4)

> They also claim that Chrome and Edge will also follow this behaviour. Safari is
> unknown, but touch on macOS doesn't seem to be a big thing anyway.

Chrome on Unix (touch) seems to follow this behavior now also.