[BUG] UW Screen with apps in center and Left/Right window fill not working
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 55/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Tranquilo
- Stack tecnológico
- macos
- Área
- desktop
Línea de trabajo
Reproduce the issue using a Samsung ultrawide display with Slack and WhatsApp centered, then invoke Fill Left and Fill Right with Chrome. Start by tracing the fillLeft and fillRight behavior using the supplied accessibility logs. Done means each window occupies only the available side area without overlapping the centered apps.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
So I have a UW Samsung monitor
BUG: I configured slack and WhatsApp in the middle of the display and I am trying to use Fill Left or Fill Rightwith Chrome and it completely ignores the apps in the center, overlapping them randomly.
Expected behaviour: Fill left or right portion of the display left by the apps already taking the middle of display, without overlapping them.
Video:
https://github.com/user-attachments/assets/57ac0ffe-720e-4877-852c-8480dba0088f
Logs:
2026-08-14T11:09:29-03:00: AX sizing proposed: (3126.0, 1440.0), result: (3126.0, 1440.0)
2026-08-14T11:09:29-03:00: AX position proposed: (-1713.0, -1440.0), result: (-1713.0, -1440.0)
2026-08-14T11:09:29-03:00: AX sizing proposed: (3126.0, 1440.0), result: (3126.0, 1440.0)
2026-08-14T11:09:29-03:00: [fillLeft], display: (-1713.0, 1107.0, 5120.0, 1440.0), calculatedRect: (-1713.0, -1440.0, 3126.0, 1440.0), resultRect: (-1713.0, -1440.0, 3126.0, 1440.0), srcScreen: C49RG9x, destScreen: C49RG9x, resultScreen: C49RG9x
2026-08-14T11:09:34-03:00: AX sizing proposed: (2560.0, 1440.0), result: (2560.0, 1440.0)
2026-08-14T11:09:34-03:00: AX position proposed: (-1713.0, -1440.0), result: (-1713.0, -1440.0)
2026-08-14T11:09:34-03:00: AX sizing proposed: (2560.0, 1440.0), result: (2560.0, 1440.0)
2026-08-14T11:09:34-03:00: [fillLeft], display: (-1713.0, 1107.0, 5120.0, 1440.0), calculatedRect: (-1713.0, -1440.0, 2560.0, 1440.0), resultRect: (-1713.0, -1440.0, 2560.0, 1440.0), srcScreen: C49RG9x, destScreen: C49RG9x, resultScreen: C49RG9x
2026-08-14T11:09:42-03:00: AX sizing proposed: (2982.0, 1440.0), result: (1994.0, 1440.0)
2026-08-14T11:09:42-03:00: AX position proposed: (425.0, -1440.0), result: (425.0, -1440.0)
2026-08-14T11:09:42-03:00: AX sizing proposed: (2982.0, 1440.0), result: (2982.0, 1440.0)
2026-08-14T11:09:42-03:00: [fillRight], display: (-1713.0, 1107.0, 5120.0, 1440.0), calculatedRect: (425.0, -1440.0, 2982.0, 1440.0), resultRect: (425.0, -1440.0, 2982.0, 1440.0), srcScreen: C49RG9x, destScreen: C49RG9x, resultScreen: C49RG9x
2026-08-14T11:09:47-03:00: AX sizing proposed: (2982.0, 1440.0), result: (2015.0, 1440.0)
2026-08-14T11:09:47-03:00: AX position proposed: (425.0, -1440.0), result: (425.0, -1440.0)
2026-08-14T11:09:47-03:00: AX sizing proposed: (2982.0, 1440.0), result: (2982.0, 1440.0)
2026-08-14T11:09:47-03:00: [fillRight], display: (-1713.0, 1107.0, 5120.0, 1440.0), calculatedRect: (425.0, -1440.0, 2982.0, 1440.0), resultRect: (425.0, -1440.0, 2982.0, 1440.0), srcScreen: C49RG9x, destScreen: C49RG9x, resultScreen: C49RG9x
2026-08-14T11:09:50-03:00: AX sizing proposed: (2560.0, 1440.0), result: (2560.0, 1440.0)
2026-08-14T11:09:50-03:00: AX position proposed: (847.0, -1440.0), result: (847.0, -1440.0)
2026-08-14T11:09:50-03:00: AX sizing proposed: (2560.0, 1440.0), result: (2560.0, 1440.0)
2026-08-14T11:09:50-03:00: [fillRight], display: (-1713.0, 1107.0, 5120.0, 1440.0), calculatedRect: (847.0, -1440.0, 2560.0, 1440.0), resultRect: (847.0, -1440.0, 2560.0, 1440.0), srcScreen: C49RG9x, destScreen: C49RG9x, resultScreen: C49RG9x
2026-08-14T11:11:04-03:00: Stopping cursor tracking (menu open: true, stashed count: 0)
2026-08-14T11:11:13-03:00: Stopping cursor tracking (menu open: false, stashed count: 0)
2026-08-14T11:12:08-03:00: Unable to find app bundle for com.apple.automator.xpc.runner
2026-08-14T11:12:46-03:00: Failed to find frontmost window.
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 156
- Forks
- 1
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
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 rxhanson/RectanglePro-Community
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
rxhanson/RectanglePro-Community#944 · 1 comentario ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
rxhanson/RectanglePro-Community#943 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
rxhanson/RectanglePro-Community#939 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
rxhanson/RectanglePro-Community#937 · 4 comentarios ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
rxhanson/RectanglePro-Community#936 · 2 comentarios ·
Todos los issues de rxhanson/RectanglePro-Community
Issues similares
-
The Browser tab fails with a Wayland error when Open Terminal runs from a Wayland desktop sessionAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
open-webui/open-terminal#210 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
flyingpie/windows-terminal-quake#419 ·
Los mantenedores suelen responder en 1 día
-
Show the per-model weekly limitAbiertoenhancement help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
[v3] KeyBindingManager calls (Add/Remove) are not converted into a case-insensitive accelerator.KeyAbiertoBug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
crmne/hyprmoncfg#114 · 1 comentario ·
Los mantenedores suelen responder en 1 día