Is your feature request related to a problem? Please describe.
Current device matching is not robust. It checks for keywords that aren't garrentied to match touchpads or touchscreens.
Describe the solution you'd like
leverage udevadm test-builtin input_id ${PATH} on all entries in /proc/bus/input/devices and check if ID_INPUT_TOUCHPAD or ID_INPUT_TOUCHSCREEN is set. can make the lookup more specific by only applying it to devices With Handlers=mouse.
Describe alternatives you've considered
It maybe possible to use KEY=4000 . or KEY=e520 . of /proc/bus/input/devices to match touchscreens and touchpads respectively. I am not sure if this matches to all devices though.
Is your feature request related to a problem? Please describe. Current device matching is not robust. It checks for keywords that aren't garrentied to match touchpads or touchscreens.
Describe the solution you'd like leverage
udevadm test-builtin input_id ${PATH}on all entries in /proc/bus/input/devices and check if ID_INPUT_TOUCHPAD or ID_INPUT_TOUCHSCREEN is set. can make the lookup more specific by only applying it to devices With Handlers=mouse.Describe alternatives you've considered It maybe possible to use KEY=4000 . or KEY=e520 . of /proc/bus/input/devices to match touchscreens and touchpads respectively. I am not sure if this matches to all devices though.