TappingDragLock timeout is not indefinite by default, is quite short, and is not configurable
TappingDragLock is governed by a timeout, and that timeout is relatively short. This is in contrast with other drivers which support TappingDragLock functionality, and don't impose any sort of timeout. I.e., the drag state remains active indefinitely until the user taps again. Furthermore, the libinput timeout is not configurable.