fix(windows): recover HUD input forwarding after startup - #387
Conversation
Re-arm click-through for HUD window after visibility to ensure input is reachable.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan includes up to 4 reviews per rolling hour; 3 remain after this review. 📝 WalkthroughWalkthroughThe HUD ChangesHUD window readiness
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This localized Windows startup recovery change is merge-ready after normal checks and review; no actionable merge-blocking risk remains. Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Re-arm the HUD's forwarded-mouse hook after the Electron window becomes visible. On Windows, the initial renderer IPC request can arrive before the native window is fully ready; if hook installation fails at that point, the HUD remains visible but all controls are unreachable.
Related issue
Refs #385
Type of change
Release impact
Desktop impact
Testing
npx tsc --noEmit— passednpx tsc -p tsconfig.test.json --noEmit— passednpx biome check --formatter-enabled=false electron/windows.ts src/components/launch/LaunchWindow.tsx src/components/launch/LaunchWindow.test.tsx— passednpx vitest --run src/components/launch/LaunchWindow.test.tsx— 32 tests passednpm run build-vite— passednpm run test— 1,769 passed, 16 failed, 2 skipped. The 16 failures are pre-existing jsdom test failures under the local Node 25 environment (`localStorage.clear/removeItem is not a function` in four unrelated test suites); no Electron test suites failed after installing the Electron binary.Summary by CodeRabbit