macOS: fullscreen Chrome Focus capture includes unselected toolbar, clips bottom, and offsets cursor
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- macos, rust
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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?
- 主要语言
- Rust
- 星标
- 25k
- 派生
- 2.4k
- 平均合并
- 1 天 11 小时
- 30 天内合并 PR
- 690
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
CapSoftware/Cap 的其他 Issue
-
Captions panel does not offer to show an existing transcript可能已有人在做 @thedavidweng 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
CapSoftware/Cap#4276 · 1 条评论 ·
维护者通常 1 天内回复
-
Download, FAQ, privacy and terms pages have no meta description可能已有人在做 @patrickballard 于 14 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
CapSoftware/Cap#3675 · 1 条评论 ·
维护者通常 1 天内回复
-
self hosting
难度 2/5 1-3 小时 新手友好度 68/100
CapSoftware/Cap#2384 · 3 条评论 ·
维护者通常 1 天内回复
-
Dashboard pagination causes full page reloads on self-hosted Cap可能已有人在做 @DipanshuAmbilkar03 于 13 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 88/100
CapSoftware/Cap#2305 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
CapSoftware/Cap#1714 · 3 条评论 ·
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
obi1kenobi/cargo-semver-checks#1814 ·
维护者通常 1 天内回复
-
community differential help wanted
难度 2/5 1-3 小时 新手友好度 68/100
hffgzktbcc-blip/ounce-core#489 · 1 条评论 ·
维护者通常 1 天内回复
-
needs triage
难度 2/5 1-3 小时 新手友好度 78/100
pbakaus/impeccable#1560 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 68/100
pact-foundation/pact-plugins#125 ·