feat(core): doubleClickDragZoom gesture

[charlieforward9]

Summary

Adds a Google/Apple Maps-style one-finger double-click/tap-and-drag zoom gesture for touch users, exposed as its own controller option:

controller: {
  doubleClickDragZoom: true
}

The gesture lets users:

1. Tap once.
2. Tap again and hold.
3. Drag vertically with the same finger to zoom continuously.

This gives mobile users a precise one-handed zoom path without requiring pinch zoom, on-screen controls, or desktop double-click zoom behavior.

Comparison Videos

Apple Maps Reference

trim.DD19513B-5915-4050-8865-99E128A9E9A0.MOV

deck.gl GlobeController Demo

trim.31AA42AB-9ACB-4104-8629-9C7557592B20.MOV

The deck.gl demo uses the same one-finger sequence against a GlobeView controller path, matching the mobile map interaction model users already expect.

Why

One-handed mobile map navigation currently has a gap: users can pan with one finger, but controlled zoom generally requires either a second finger or visible zoom controls. The double-click/tap-and-drag gesture is a standard mobile map pattern and lets users zoom in or out while keeping their thumb on the map.

While validating on iOS Safari, repeated touch gestures could also trigger page-level selection/callout affordances over the canvas. This PR keeps the gesture path inside deck.gl while leaving browser UI guard CSS to app developers, with reusable guidance documented for apps using deck.gl controllers.

What Changed

• Adds the doubleClickDragZoom controller option, defaulting to true.
• Adds a DOUBLE_CLICK_DRAG pointer-event gesture path through pointer down, move, up, and cancel handling.
• Promotes a stored tap into a one-finger zoom session when the second tap lands within the timing and distance thresholds.
• Maps vertical drag distance to zoom using DOUBLE_CLICK_DRAG_PIXELS_PER_ZOOM = 120.
• Suppresses the trailing dblclick after the drag gesture so release does not apply a second zoom.
• Short-circuits pan handling while a double-click-drag zoom session is active.
• Hardens the website GlobeView example with app-owned mobile touch CSS and canvas-scoped browser UI event guards.
• Documents doubleClickDragZoom in the Controller API.
• Moves the mobile browser touch UI docs to developer-guide/tips-and-tricks.md#optimization-for-mobile and links to that guidance from controller.md.
• Leaves default Deck canvas styling unchanged so apps opt into browser UI guards themselves.

Behavior Notes

• doubleClickDragZoom controls this gesture independently from doubleClickZoom and touchZoom.
• Works when doubleClickZoom: false, because the gesture is continuous pointer-driven zoom rather than double-click zoom.
• Works when pinch touchZoom is disabled, because this is a distinct one-finger gesture.
• Keeps desktop mouse and keyboard behavior unchanged.
• Uses the shared controller path, so controllers can opt into the same gesture behavior.
• Avoids app-level pointer propagation changes, preserving the existing deck.gl event manager and context-menu behavior.
• Keeps the local satellite GlobeView comparison demo out of the PR; only reusable core behavior plus docs/example hardening is included.

Validation

• Added MapController supports double-click drag zoom when double click and touch zoom are disabled, covering the full pointer sequence and release behavior.
• Added MapController disables double-click drag zoom, covering the new controller option gate.
• Focused local test:

yarn test -- test/modules/core/controllers/controllers.spec.ts test/modules/core/lib/deck.spec.ts

• Commit hook validation ran repository lint/prettier checks and node smoke tests. Existing lint warnings were reported, with no errors.
• git diff --check
• Local Docusaurus dev server compiled and served the docs at http://127.0.0.1:3000/ with placeholder map API env vars; only dependency source-map warnings from arc were reported.
• Local mobile demo validation was run against a satellite GlobeView setup to compare the gesture against Apple Maps-style interaction. That demo was intentionally kept out of this PR to avoid adding example bloat.

Merge Notes

This is intentionally scoped to the reusable one-finger double-click/tap-and-drag zoom gesture, the dedicated controller option, and app-owned docs/example interaction hardening discovered during mobile validation. GlobeView pointer anchoring/parity work is handled separately in #10307, and the local comparison demo combined the two branches only for manual mobile validation.

[coveralls]

coverage: 83.386%. remained the same — NEW-HEAT:codex/touch-double-tap-zoom into visgl:master

[chrisgervang]

For follow up, does mjoinir need a 'dblclickmove'? There isn't a second up pointer event so I'm not sure

[chrisgervang]

@Pessimistress suggested a good refactor would be to implement a new recognizer in mjolnir for this. It'd simplify the controller compared to using raw pointer events.

[charlieforward9]

Id like to gain some perspective on how platforms like  OS organize their gesture recognition across mobile, mouse, and Vision Pro, I strongly agree gesture recognition should be managed within mjolnir.