Tap maxDelay default differs between web/docs (500 ms) and Android/iOS (200 ms). Which is intended?

[Shexter]

While reading the Tap handler across platforms I noticed the default for maxDelay (the time allowed before the next tap in a multi-tap gesture) isn't the same everywhere:

Where	Default	Location
Docs	500 ms	docs-gesture-handler/docs/gestures/use-tap-gesture.mdx:112
Web	500 ms	src/web/handlers/TapGestureHandler.ts:10
Android	200 ms	android/.../core/TapGestureHandler.kt:190
iOS/macOS	200 ms	apple/Handlers/RNTapHandler.m:51

So useTapGesture({ numberOfTaps: 2 }) gives a 500 ms window on web but 200 ms on native, and the docs describe only the web value. (Checked against main at 71df747.)

Is the difference intentional? If so I'd send a docs PR noting the per-platform defaults. If 200 ms or 500 ms is meant to be the single default, I'm happy to send a PR aligning the rest. I didn't want to change a behaviour default without checking first.

[m-bert]

Hi @Shexter! Good catch!

Is the difference intentional?

No, it is not 😅

If 200 ms or 500 ms is meant to be the single default, I'm happy to send a PR aligning the rest.

Of course! The default should be 200, since this is the value that was decided to be default on the mobile 😅 Let me know when the PR is ready!

[Shexter]

Thanks! The PR is up: #4557