[Feature]: Doesn't work on multi-monitor.

[0xNull-ops]

Problem

I'm running an M4 with two screens and it does not work with multi-monitors.

It is unclickable.

Proposed solution

Add multi-monitor support.

Platform impact

Windows

Constraints or privacy notes

No response

[Leonxlnx]

Triage note: not closing this yet. Current main still needs a dedicated native multi-monitor pass. The latest work keeps right/left/top docking and pointer passthrough covered by smoke/native build checks, but real per-monitor placement/clickability should be fixed and verified separately on multi-screen Windows/macOS hardware.

[Leonxlnx]

Shipped a native-side monitor targeting improvement in d734233: the app now resolves the monitor under the cursor with Tauri monitorFromPoint before falling back to currentMonitor, and the click-through hit test uses the same monitor scale factor. Verified lint, build, smoke tests, native release build, and project verify locally. Keeping this open until it is confirmed on a real multi-monitor setup.

[Leonxlnx]

Follow-up in 6365b1f/9bb49dd: native startup now also picks the monitor under the cursor before falling back to current_monitor, and project verification now checks for both monitorFromPoint usage and the required Tauri permission. Local Windows native release build passed. Still leaving the issue open until real multi-monitor hardware confirms the behavior.

[Leonxlnx]

v0.1.7 has been verified through local Windows native no-bundle build plus GitHub Windows/macOS CI, and the previous native monitor targeting work remains in this release. Keeping this open until it is confirmed on real multi-monitor hardware because CI cannot prove clickability on physical display edge cases.