Comment 25 for bug 270002

Thanks for finding a reasonable fix to this problem. The root culprit is likely that during two- and three-finger taps, many touchpad drivers lose track of which finger is the tracking one. This results in sudden jumps of the
pointer, which due to the MaxTapMove logic cancels the tapping action. The reasonable default otherwise is something like a finger wide, which is what the new auto-set defaults will give you in the next upstream release. I will have a look at the possibility to fix the tracking finger better, since this would also remove the disturbing behavior of a moving pointer during multi-finger actions.

On a different note, I have trouble seeing how

        Option "MaxTapMove" "0"

can work, since it counteracts the idea behind MaxTapMove.