Area picker does not work anymore

[Nathan-Wrpt]

When clicking then dragging to select the area, the click just releases automatically a few milliseconds later.
It occurs in both the screenshot area picker and the area picker for recording purposes.

Here is a recording of me trying to screenshot an area on my screen. You can't see the area picker overlay since cap blocks it from being recorded, but you can get the issue with the video:
https://github.com/user-attachments/assets/dc48f25e-cc9c-4962-9286-425acc2bc455

Have a nice and lovely day!

[linear]

CAP-731

[tembo]

The area selection logic lives in apps/desktop/src/components/Cropper.tsx, which is used by the target select overlay at apps/desktop/src/routes/target-select-overlay.tsx.

Recent commits on June 8th refactored the drag handling to use pointer capture (setPointerCapture/releasePointerCapture) in commits 42933cc and 9c204e5. The trackPointerSession function (around line 686-724 in Cropper.tsx) now listens for lostpointercapture events and ends the drag session when pointer capture is lost. If something is causing pointer capture to be lost prematurely, that would explain the click releasing automatically.

This could be related to some existing open issues:

• Area selector not working with external monitors #595 - Area selector not working with external monitors
• Issues with regions and multiple screens #381 - Issues with regions and multiple screens
• Multi-monitor problems #340 - Multi-monitor problems

A few questions that would help narrow this down:

• What OS and version are you running?
• Are you using multiple monitors or an external display?
• Did this start happening after a recent update, or is this a fresh install?

If you're on a multi-monitor setup, the overlay window spanning monitors or losing focus could cause pointer capture to be released unexpectedly.

[Nathan-Wrpt]

The area selection logic lives in apps/desktop/src/components/Cropper.tsx, which is used by the target select overlay at apps/desktop/src/routes/target-select-overlay.tsx.

Recent commits on June 8th refactored the drag handling to use pointer capture (setPointerCapture/releasePointerCapture) in commits 42933cc and 9c204e5. The trackPointerSession function (around line 686-724 in Cropper.tsx) now listens for lostpointercapture events and ends the drag session when pointer capture is lost. If something is causing pointer capture to be lost prematurely, that would explain the click releasing automatically.

This could be related to some existing open issues:

• Area selector not working with external monitors #595 - Area selector not working with external monitors
• Issues with regions and multiple screens #381 - Issues with regions and multiple screens
• Multi-monitor problems #340 - Multi-monitor problems

A few questions that would help narrow this down:

• What OS and version are you running?
• Are you using multiple monitors or an external display?
• Did this start happening after a recent update, or is this a fresh install?

If you're on a multi-monitor setup, the overlay window spanning monitors or losing focus could cause pointer capture to be released unexpectedly.

• Windows, last version.
• I am using three monitors.
• Started happening after the last update.

[Nathan-Wrpt]

For your information, I tried on another PC with a fresh installation, and the problem still occurs with multiple monitors, but does not when I am on a single monitor setup.

[richiemcilroy]

Hmm strange - it must be because it's being excluded in your setup. Try removing it from the exclusion list in Settings -> General -> Excluded windows in Cap?

Let me know how that goes

[wubie052]

That's definitely the exact same issue. I'm also running Windows on a dual-monitor setup and selected 'Area Mode'.#1945

[wubie052]

In issue #1945, Tembo's AI pinpointed the code likely responsible for this bug and suggested a potential fix.

[wubie052]

Also, just to add to this: the bug is also triggered when returning from the Settings window while in Studio mode, or when Display mode is selected.