Devs love the symmetry of their touch handling code and often have the finger-down, finger-moved, and finger-up callbacks from the system all call the same handleTouch function they wrote. As you can tell, however, the touch from the finger up callback is often better discarded or handled differently otherwise you get these sort of bugs
Unfortunately, it's still bad. It's a bit better than dragging the handles of the selected area, but if I go to far and want to reduce the selected area, it doesn't work anymore.
> You just wanted to move the cursor. Now everything is selected.
> You want to position the cursor at the end of a line. You tap. It selects the last word. You try to grab the handle — it doesn't respond and deselects. You tap again, now it selects the whole sentence. You tap blank space to deselect — nothing. You tap five more times. On the fifth, it selects all. You switch apps hoping the selection disappears. You tap and hold — sometimes text selects, sometimes a menu appears, sometimes nothing. Got a Magic Keyboard? Good luck — trackpad selection just doesn't work half the time, but touching the screen does. Eventually you select all, delete everything, and retype from scratch. Apple has had 17 years to figure out touch text selection. This is where they landed.