macOS: fullscreen Chrome Focus capture includes unselected toolbar, clips bottom, and offsets cursor
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- macos, rust
- Domain
- computer-graphics, desktop
Research direction
Start with crates/recording/src/sources/screen_capture/macos.rs and compare the ScreenCaptureKit source rectangle with the picker bounds from apps/desktop-gpui/src/target_overlay.rs; then check cursor cropping in crates/recording/src/cursor.rs. Reproduce the reported fullscreen Chrome case and inspect the captured frame geometry alongside cursor coordinates. Done means the recording matches the selected bounds, including the bottom edge, and the cursor stays aligned.
Written by the indexing model from the issue text.
Description
Description
Focus window recording of Chrome in its fullscreen/maximized state does not match the blue capture-selection rectangle on macOS. The picker selects the page content below Chrome's tabs/address toolbar, but the resulting recording includes that toolbar and loses a corresponding portion of the bottom of the selected content. The recorded cursor also has a persistent upward offset, even after the mouse stops moving.
This is consistently reproducible in manual testing. A normal, non-maximized Chrome window records accurately whether Cap's setup window is on the same display or a different display. This suggests that placing the setup window on another monitor alone is not sufficient to trigger the problem.
Reproduction
- Use Chrome on a Mac with multiple displays.
- Put Chrome into the fullscreen/maximized state in which Cap's setup controls cannot remain visible alongside it on the same display, and place Cap's setup window on another display.
- Select the Chrome window for Studio recording with Focus enabled. Center on screen was also enabled in the reported example; its independent effect has not been isolated.
- Observe the blue selection rectangle: it excludes the browser's tabs/address toolbar and covers the page-content area. One example shows 1920 × 992 selected within a 1920 × 1080 screen image, excluding approximately 88 pixels at the top.
- Record the window, moving the pointer to recognizable controls and letting it stop.
- Compare the actual recording with the blue selection rectangle and the controls the pointer was over.
- Repeat with Chrome as a normal, non-maximized window as a control case.
The fullscreen/maximized description above identifies the observed window state; other macOS zoom/fill variants have not been separately isolated.
Expected behavior
The recorded frame should match the selected blue bounds, preserve their bottom edge, and keep the cursor aligned with the actual UI targets.
Actual behavior
- Browser chrome above the selected bounds appears in the recording.
- Content near the bottom of the selected bounds is cut off.
- The cursor is consistently displaced upward relative to the recorded UI, including while stationary.
- The normal-window control case records correctly with either same-display or cross-display setup controls.
This is a capture-area mismatch as well as a cursor-placement issue; shifting cursor metadata alone cannot recover the omitted bottom content.
Additional Context
- Cap: 0.6.3
- macOS: 27.2.1
- Google Chrome: 157.0.8103.79
- Device: Apple Silicon MacBook with multiple displays
- Mode: Studio, window capture, Focus enabled
The original screenshots contain internal work documents/account information and are not attached here.
Source investigation — suspected cause, not a verified fix
The following code paths appear relevant:
- The picker's window bounds come from
display_relative_logical_bounds(), ultimately based onkCGWindowBounds. - Focus capture creates a ScreenCaptureKit
desktopIndependentWindowfilter. Its source rectangle uses a local(8, 8)origin and dimensions derived from the CG window bounds. - The cursor crop continues to use the current CG window origin.
- Chromium's native fullscreen implementation moves the top toolbar out of the main content view into an AppKit fullscreen window.
A possible explanation is that the CG-selected content rectangle and the actual SCK window surface have different origins/extents in this fullscreen case. Treating them as equivalent would explain all three symptoms: extra toolbar, missing bottom content, and a uniform cursor offset. The actual SCK frame geometry for the failing fullscreen recording has not been captured, so the precise SCK composition/cropping behavior is still a hypothesis.
Related: #4254 removes the 8-point corner trim. I also inspected main at abba000, where the independent-window source origin is (0, 0). I have not verified a nightly build or established that this related change resolves the fullscreen toolbar-height discrepancy.
Could the selected bounds, actual window-surface crop, and cursor mapping be checked together for this fullscreen Chrome case?
- Dominant language
- Rust
- Stars
- 25k
- Forks
- 2.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 690
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CapSoftware/Cap
-
Captions panel does not offer to show an existing transcriptPossibly taken @thedavidweng claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
CapSoftware/Cap#4276 · 1 comment ·
Maintainers usually reply within 1 day
-
Download, FAQ, privacy and terms pages have no meta descriptionPossibly taken @patrickballard claimed this 14 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
CapSoftware/Cap#3675 · 1 comment ·
Maintainers usually reply within 1 day
-
self hosting
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CapSoftware/Cap#2384 · 3 comments ·
Maintainers usually reply within 1 day
-
Dashboard pagination causes full page reloads on self-hosted CapPossibly taken @DipanshuAmbilkar03 claimed this 12 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
CapSoftware/Cap#2305 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CapSoftware/Cap#1714 · 3 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oxc-project/tsrs#1010 ·
Maintainers usually reply within 1 day
-
Link is deadOpen
Difficulty 1/5 Under an hour Newbie friendliness 63/100
nicholas-ochoa/OpenSC2K#104 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
libracoder/kiri#445 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DioxusLabs/blitz#1614 ·
Maintainers usually reply within 1 day