Bug 505471

Summary: Handles of selection show up in screencasts
Product: [Applications] Spectacle Reporter: Paul Brown <paul.brown>
Component: GeneralAssignee: Noah Davis <noahadvs>
Status: CONFIRMED ---    
Severity: normal CC: asdf-kd, kde, nate, olib141
Priority: NOR    
Version First Reported In: 6.3.91   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: A screenshot of Haruna playing a screen recording. You can see the resize handles along the top of the frame

Description Paul Brown 2025-06-11 12:09:37 UTC
Created attachment 182185 [details]
A screenshot of Haruna playing a screen recording. You can see the resize handles along the top of the frame

SUMMARY

When you select an area of the screen to record and move the selection area to an edge or corner of the screen, the handles you use to resize the box show up in the recording as you can see from the attached screenshot.

STEPS TO REPRODUCE
1. Open Spectacle
2.  Chose "New Recording"
3. Select area
4. Move area to edge or corner of the screen
5. Start recording
6. Stop recording and save

OBSERVED RESULT

The handles of the selection rectangle adjacent to the edges will show up in the recording.

EXPECTED RESULT

That the handles would become invisible, as when you capture a static screenshot.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Oliver Beard 2025-06-11 13:59:22 UTC
Can reproduce — this happens only when a rectangular region is against the edges, as the handles appear to move away from the edges to be draggable (they include a cutout to not overlap the region).
Comment 2 Nate Graham 2025-06-12 15:21:08 UTC
Can also reproduce.
Comment 3 Noah Davis 2025-06-12 15:22:46 UTC
unfortunately, I am not able to reproduce this.
Comment 4 Filip 2025-07-18 10:50:58 UTC
*** Bug 507179 has been marked as a duplicate of this bug. ***