React Native hitSlop — extra hit-test area OUTSIDE the painted box.
A control's comfortable touch target and its visual weight are different numbers. A 20pt-tall switch or a 16pt-tall slider looks right and is hard to hit; growing the box to fix that would change the layout and the look. hit_slop grows only the area hit_test() accepts, so the painted control, its bounds, and the Yoga layout are all untouched.
The insets are in the view's OWN coordinate space (post-scale), in points, one per edge, and are applied in two places: a parent uses a child's slop to decide whether to descend into it, and the view uses its own to decide whether a point that missed local_bounds() still counts as a hit. Both are required — inflating only the terminal check leaves the parent refusing to descend, so the slop would never be consulted.
Slop does NOT change paint, layout, focus order, or accessibility bounds, and it does not let a PointerEvents::none view become hittable. Overlapping slop resolves the same way overlapping boxes do: topmost in z-order wins, because slop is evaluated inside the existing reverse-z walk rather than beside it.
pulp::view::HitMetrics supplies the device-appropriate figures — a 44pt touch target for a 16pt control means 14pt of slop per edge.
1.15.0