cc-ing sadrul@ in the likely case he knows what's going on here.

I have an Acer T230H touchscreen, and touch works as expected in chrome (in both attached and floating mode). Try floating the touchscreen device 'xinput float 10' (you can undo by 'xinput reattach 10 2'), and see if that helps.

Also, can you run 'xinput test-xi2', use the touchscreen for a bit, and attach the output in this bug? (when you touch the screen, you should see TouchBegin/TouchUpdate/TouchEnd events in the log)

PS: consider running with a different profile (e.g. with this flag: --user-data-dir=/tmp/chrome-test) to make sure some setting from chrome:flags isn't affecting it.

For me it works in floating mode but not attached mode.  Same in a fresh profile.  xinput test-xi2 logs in both modes are attached, though I do not see TouchBegin/TouchUpdate/TouchEnd events in either mode.  I’m using a ThinkPad Yoga 14 type 20FY.

Deleted: test-xi2-attached.txt 136 KB

test-xi2-attached.txt 136 KB View Download

Deleted: test-xi2-floating.txt 54.0 KB

test-xi2-floating.txt 54.0 KB View Download

With attached, it looks like x11 is not sending touch events even in 'xinput test-xi2'. So there's not a lot chrome can do about it if x11 isn't sending the right events.

I'm having a similar problem with a Surface Pro 3 running Fedora 25 beta, which uses Gnome on Wayland by default. Touch behavior works as expected in all Gnome apps, but Chromium does not respond to tapping and pinching. Sometimes it partially responds with a 'hover' behavior, e.g., showing a tooltip in my bookmarks bar. (When reverting to Gnome on Xorg, Chromium behaves as expected.)

xinput reports:
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ xwayland-pointer:14                     	id=6	[slave  pointer  (2)]
⎜   ↳ xwayland-touch:14                       	id=8	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ xwayland-keyboard:14                    	id=7	[slave  keyboard (3)]

Running with --touch-devices=8 or 2 does not change anything; also tried with a new user profile as suggested above.

xinput test-xi2 produces output as expected, like this for a simple tap:
EVENT type 22 (RawTouchBegin)
    device: 2 (8)
    detail: 95
    valuators:
          0: 82.00 (82.00)
          1: 212.00 (212.00)

EVENT type 7 (Enter)
    device: 2 (8)
    windows: root 0x273 event 0x1400001 child 0x0
    mode: NotifyNormal (detail NotifyVirtual)
    flags: [focus] [same screen]
    buttons:
    modifiers: locked 0 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  81.00 / 211.00
    event x/y: 81.00 / 82.00
EVENT type 6 (Motion)
    device: 2 (8)
    detail: 0
    flags: emulated
    root: 81.98/211.85
    event: 81.98/82.85
    buttons:
    modifiers: locked 0 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    valuators:
        0: 82.00
        1: 212.00
    windows: root 0x273 event 0x1400001 child 0x1400002
EVENT type 8 (Leave)
    device: 2 (8)
    windows: root 0x273 event 0x1400001 child 0x0
    mode: NotifyNormal (detail NotifyVirtual)
    flags: [focus] [same screen]
    buttons:
    modifiers: locked 0 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  81.00 / 211.00
    event x/y: 81.00 / 82.00
EVENT type 23 (RawTouchUpdate)
    device: 2 (8)
    detail: 95
    valuators:
          0: 82.00 (82.00)
          1: 212.00 (212.00)

EVENT type 24 (RawTouchEnd)
    device: 2 (8)
    detail: 95
    valuators:
          0: 82.00 (82.00)
          1: 212.00 (212.00)

Seems like everything is basically there but Chromium still doesn't know where to find the touch device input even when forced with --touch-devices ... might there be another simple workaround to give it a shot? This is the only thing stopping me from using Wayland full-time.

By the way, this occurs both with the build that ships with Fedora 25beta (53.x) and a recent developer build: 54.0.2840.59

It also occurred with the Chromium build that ships with Fedora 24 (on Wayland), before I upgraded to 25beta.

update: touch works again with the latest updates to Fedora25 beta (presumably to Xwayland) and Chromium 54.0.2840.59. For reference, xinput now reports:
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ xwayland-pointer:14                     	id=6	[slave  pointer  (2)]
⎜   ↳ xwayland-relative-pointer:14            	id=7	[slave  pointer  (2)]
⎜   ↳ xwayland-touch:14                       	id=9	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ xwayland-keyboard:14                    	id=8	[slave  keyboard (3)]

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot