navigator.vibrate (Android Chrome/PWA only; iOS has no web vibration API — no-op there).
Scope
PTT: 10 ms tick on engage, 10 ms on release (useCallHotkeys PTT paths + the on-screen PTT chip).
Reactions: 8 ms tick when a reaction is sent from the hover/quick bar or the emoji board.
Single helper utils/haptics.ts with tick(kind); guarded by 'vibrate' in navigator, prefers-reduced-motion respected (no haptics), and a Settings → General toggle "Haptic feedback" (default on) only rendered when the API exists.
`navigator.vibrate` (Android Chrome/PWA only; iOS has no web vibration API — no-op there).
### Scope
- PTT: 10 ms tick on engage, 10 ms on release (`useCallHotkeys` PTT paths + the on-screen PTT chip).
- Reactions: 8 ms tick when a reaction is sent from the hover/quick bar or the emoji board.
- Single helper `utils/haptics.ts` with `tick(kind)`; guarded by `'vibrate' in navigator`, `prefers-reduced-motion` respected (no haptics), and a Settings → General toggle "Haptic feedback" (default on) only rendered when the API exists.
jared
added this to the Features 2026-Q4 milestone 2026-09-17 15:43:35 -04:00
utils/haptics.tstick('ptt-on' | 'ptt-off' | 'reaction') → navigator.vibrate(10 / 10 / 8 ms); no-op without the API (iOS), under prefers-reduced-motion, or when Settings → Calls → Haptic Feedback (default on, rendered only where the API exists) is off. PTT is observed once through pttActiveAtom, so the keyboard, global-hotkey and on-screen-chip paths all tick on engage and release; reactions tick at the point the reaction event is sent in the room and thread timelines (hover bar, quick bar, touch sheet and emoji board all funnel there). Unit tests for the guard logic; headless on Pixel 7 emulation with a stubbed navigator.vibrate: sending 👍 from the long-press sheet → vibrate(8).
Done in 492b57c6.
`utils/haptics.ts` `tick('ptt-on' | 'ptt-off' | 'reaction')` → `navigator.vibrate(10 / 10 / 8 ms)`; no-op without the API (iOS), under `prefers-reduced-motion`, or when Settings → Calls → **Haptic Feedback** (default on, rendered only where the API exists) is off. PTT is observed once through `pttActiveAtom`, so the keyboard, global-hotkey and on-screen-chip paths all tick on engage and release; reactions tick at the point the reaction event is sent in the room and thread timelines (hover bar, quick bar, touch sheet and emoji board all funnel there). Unit tests for the guard logic; headless on Pixel 7 emulation with a stubbed `navigator.vibrate`: sending 👍 from the long-press sheet → `vibrate(8)`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
navigator.vibrate(Android Chrome/PWA only; iOS has no web vibration API — no-op there).Scope
useCallHotkeysPTT paths + the on-screen PTT chip).utils/haptics.tswithtick(kind); guarded by'vibrate' in navigator,prefers-reduced-motionrespected (no haptics), and a Settings → General toggle "Haptic feedback" (default on) only rendered when the API exists.Done in
492b57c6.utils/haptics.tstick('ptt-on' | 'ptt-off' | 'reaction')→navigator.vibrate(10 / 10 / 8 ms); no-op without the API (iOS), underprefers-reduced-motion, or when Settings → Calls → Haptic Feedback (default on, rendered only where the API exists) is off. PTT is observed once throughpttActiveAtom, so the keyboard, global-hotkey and on-screen-chip paths all tick on engage and release; reactions tick at the point the reaction event is sent in the room and thread timelines (hover bar, quick bar, touch sheet and emoji board all funnel there). Unit tests for the guard logic; headless on Pixel 7 emulation with a stubbednavigator.vibrate: sending 👍 from the long-press sheet →vibrate(8).