Hide safe gaps after drag threshold

[ruggi]

Fixes #4253

Problem:

1. Safe gaps are immediately hidden when an interaction starts, but that can become clunky when i.e. double-clicking a text element to enter edit mode.
2. Text elements always show safe gaps, but this is not necessarily a good thing (they are below the small element threshold).

Fix:

1. Hide the safe gaps only after the drag threshold is met
2. Only show safe gaps for text elements that were resized past their initial max-content dimensions

Screen.Recording.2023-09-28.at.1.19.52.PM.mov

[github-actions]

Try me

[relativeci]

Job #8298: Bundle Size — 62.67MiB (~+0.01%).

bbb6d0f(current) vs 5957b21 master#8294(baseline)

⚠️ Bundle contains 64 duplicate packages

Metrics (2 changes)

	Current Job #8298	Baseline Job #8294
Initial JS	34.94MiB(~+0.01%)	34.93MiB
Initial CSS	0B	0B
Cache Invalidation	18.35%	0%
Chunks	27	27
Assets	31	31
Modules	3970	3970
Duplicate Modules	422	422
Duplicate Code	30.84%	30.84%
Packages	409	409
Duplicate Packages	64	64

Total size by type (1 change)

	Current Job #8298	Baseline Job #8294
CSS	0B	0B
Fonts	0B	0B
HTML	11.43KiB	11.43KiB
IMG	0B	0B
JS	62.66MiB (~+0.01%)	62.66MiB
Media	0B	0B
Other	0B	0B

---

View job #8298 report View fix/safe-gaps-after-threshold branch activity

[github-actions]

Performance test results:

[balazsbajorics]

I like the new behavior! but I wouldn't add hasBeenPastThreshold to the interactionState to avoid inflating it and instead use drag != null.

[ruggi]

I like the new behavior! but I wouldn't add hasBeenPastThreshold to the interactionState to avoid inflating it and instead use drag != null.

oh man, nice! yeah I added that because I did not figure out the != null part, it actually solves it! removed hasBeenPastThreshold in b341491 (#4254)