macOS: fullscreen Chrome Focus capture includes unselected toolbar, clips bottom, and offsets cursor
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- macos, rust
- Área
- computer-graphics, desktop
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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?
- Lenguaje dominante
- Rust
- Estrellas
- 25k
- Forks
- 2.4k
- Merge medio
- 1 d 11 h
- PR fusionados (30 d)
- 690
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de CapSoftware/Cap
-
Captions panel does not offer to show an existing transcriptPosiblemente ocupada @thedavidweng la tomó hace 1 día. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
CapSoftware/Cap#4276 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Download, FAQ, privacy and terms pages have no meta descriptionPosiblemente ocupada @patrickballard la tomó hace 14 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
CapSoftware/Cap#3675 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
self hosting
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
CapSoftware/Cap#2384 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dashboard pagination causes full page reloads on self-hosted CapPosiblemente ocupada @DipanshuAmbilkar03 la tomó hace 12 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
CapSoftware/Cap#2305 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
CapSoftware/Cap#1714 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de CapSoftware/Cap
Issues similares
-
good first issue help wanted
Dificultad 1/5 Menos de una hora Aptitud para principiantes 87/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
jolars/panache#627 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
swc-project/swc-next-issues#490 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
oxc-project/tsrs#1010 ·
Los mantenedores suelen responder en 1 día
-
Link is deadAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 63/100
nicholas-ochoa/OpenSC2K#104 ·