Skip to content

Add touch slop and hit-test for marker presses#83

Open
dacoto wants to merge 1 commit into
lugg:mainfrom
dacoto:fix/android-marker-press-latency
Open

Add touch slop and hit-test for marker presses#83
dacoto wants to merge 1 commit into
lugg:mainfrom
dacoto:fix/android-marker-press-latency

Conversation

@dacoto

@dacoto dacoto commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Track touch DOWN/UP to detect taps vs. moves and perform hit-testing to find nearest marker within a configurable radius. Introduces tapDownPoint and earlyFiredMarker to avoid duplicate press events, computes hit center based on marker icon height, and fires a synthetic press via fireMarkerPressIfNearby. Adds TAP_SLOP_PX and HIT_RADIUS_DP constants and updates existing press handling to ignore markers already fired early.

Summary

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update

Test Plan

Screenshots / Videos

Checklist

  • I tested on iOS
  • I tested on Android
  • I tested on Web
  • I updated the documentation (if needed)

Track touch DOWN/UP to detect taps vs. moves and perform hit-testing to find nearest marker within a configurable radius. Introduces tapDownPoint and earlyFiredMarker to avoid duplicate press events, computes hit center based on marker icon height, and fires a synthetic press via fireMarkerPressIfNearby. Adds TAP_SLOP_PX and HIT_RADIUS_DP constants and updates existing press handling to ignore markers already fired early.
@lodev09

lodev09 commented Jun 10, 2026

Copy link
Copy Markdown
Collaborator

@dacoto I'm wondering what's the use-case here and what are you trying to solve/fix? Just want to understand the changes that might affect tap behavior. Do you have some video that I can look?

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants