Increased the collapsed check timeout on pointerup

[oleksandr-danylchenko]

Issue

Source - #136 (comment)

Unfortunately, I noticed that the "lagging behind isCollapsed property" is still a thing for touch devices! When I tap somewhere around the selection - the isCollapsed is still true when the onPointerUp gets handled, even within the setTimeout.

That creates a weird effect that makes a user tap twice to dismiss the selection. Similar to the one we had in the demos above ;(

Changes Made

Source - #136 (comment)

Incredibly... increasing the setTimeout's timeout from the default 0 to 1 helps! It starts reporting the isCollapsed properly again!

UPD: Turned out that 1ms. isn't always enough, so I switched to the 5ms. delay instead

[oleksandr-danylchenko]

I think that approach should be more flexible here...
I discovered that on iOS it takes up to 40ms to properly report that the selection range is collapsed even when a user clicks beyond the existing selection! But if we decide to apply such a timeout universally - it'll make user experience on desktops and Androids slower in general.
Instead, we may wanna have a "polling" for the range collapse state 🤔. If the timeDifference is smaller than the CLICK_TIMEOUT and the range isn't collapsed - we start polling it for up to 50ms. (to be extra cautious). So if the browser changes its state quicker - it won't be held off by a "blind" timeout.