Gnome's default web browser, Epiphany, works very poorly with our HTML client. Some of the issue I've found:
- I get error code 1006 for my test server. Certificate issues?
- I get the touch controls (mouse button selector, etc.)
- Mouse doesn't seem to work. Possibly because it is hoping for touch events.
- Some keys don't work, e.g. Escape
(In reply to comment #0)
>- I get error code 1006 for my test server. Certificate issues?
Yep: I see this in the console: "WebSocket network error: Unacceptable TLS certificate"
>- I get the touch controls (mouse button selector, etc.)
Gnome doesn't seem to want to leave it up to the webpage to decide if the device is touch or not. Epiphany always acts like it's on a touch device.
>- Mouse doesn't seem to work. Possibly because it is hoping for touch events.
Correct, I did a quick test, and it works in noVNC after applying the changes proposed here https://github.com/kanaka/noVNC/pull/619
>- Some keys don't work, e.g. Escape
I tested eudemo's WebAccess in epiphany on Fedora 28 today. Can't see any keyboard or mouse problems. No certificate complaints either, but eudemo has a proper cert.
The only remaining problem I can see is that I get the touch controls without having a touch screen.
This was resolved in commit r39346 as part of bug 7908. The way we detect touch has been reworked and things appear to be more reliable here. The mobile-only on screen keyboard button no longer incorrectly show on Epiphany when used without a touch screen.
I tested Epiphany 43.1 on Fedora 37.
bug 8024 comment 6 and 7.
The new method was tested as part of bug 7908 on iPadOS, Android, Windows (no touch), Windows (touch) and macOS (see bug 7908 comment 535 and following comments):
* The virtual keyboard button appears on devices with a touch screen
* The virtual keyboard button does not appear on devices without a touch screen
Apart from determining whether the virtual keyboard button should be shown or not, the new touch detection method is also used to determine if we should show :hover styles on buttons and similar.
Note that, while resolving some issues, the new method introduces at least one new problem:
Keyboard button has disappeared on mobile in the latest release
Note that the device in question in the upstream issue is a fairly uncommon “Microsoft Surface Duo”. We haven't seen issues with other devices yet.