[go: nahoru, domu]

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chromium-ozone-wayland does not detect touchscreen pointer device #645

Open
apbr opened this issue Jul 19, 2022 · 2 comments
Open

chromium-ozone-wayland does not detect touchscreen pointer device #645

apbr opened this issue Jul 19, 2022 · 2 comments

Comments

@apbr
Copy link
apbr commented Jul 19, 2022

I use chromium-ozone-wayland version: 96.0.4664.110
I start chromium-ozone-wayland with
/usr/bin/chromium --kiosk --noerrdialogs --no-first-run --enable-wayland-ime --autoplay-policy=no-user-gesture-required http://localhost:80

To check which pointer type is recognized by chrome following JavaScript code can be used:

// True if at least one coarse pointer device exists.
matchMedia('(pointer:coarse)').matches;
// True if at least one fine pointer device exists.
matchMedia('(pointer:fine)').matches;

As I understand it, websites adapt their style according to the detected pointer device of the browser.
A mouse or a touchpad is a fine pointer device. Touchscreens are coarse pointer devices.

My device has a touchscreen.
Observed behaviour:
Chromium detects neither a coarse nor a fine pointer device. If I connect a mouse it only detects a fine pointer device.
Expected behaviour:
Chromium should always detect a coarse pointer device as the touchscreen is always present.

Is there any flag I have to pass to chromium or anything I have to change in my system to fix this?

@rakuco
Copy link
Collaborator
rakuco commented Aug 5, 2022

Chromium 96 is pretty old by Chromium's standards, so I'd start by trying a newer release. Additionally: is it possible to test an official Google Chrome release for your platform and see if that one works as expected?

@apbr
Copy link
Author
apbr commented Aug 9, 2022

I can reproduce it with 103.0.5060.129-r0.
Unfortunately I can't easily test an official Google Chrome release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants