> They just see the X11 driver allowing them to define their own areas etc on a touchpad, while libinput does not. That's one specific X11 driver for a few spe

> They just see the X11 driver allowing them to define their own areas etc on a touchpad, while libinput does not. That's one specific X11 driver for a few specific touchpad devices and with no user interface to configure. I doubt if more than a handful of users ever bothered to read the manpages to find out about this functionality, much less actually define their own touchpad regions. I'm sure there are a few exceptions, but the vast majority of the users just use the defaults or tweak whatever settings Gnome/KDE exposes in their UI. In fact, the mere fact that an X11 touchpad driver provides this functionality is actually proof of why X11 has outlived its usefulness. Touchpad regions do not belong to the touchpad driver. They belong to the layer that interprets touchpad input above that - it should be a desktop-environment feature that works with all touchpads, not a driver feature that works with a single touchpad make. Libinput is correct in not providing a kitchensink.