headed chrome can't be quit from macOS dock and also blocks user from creating new chrome windows

Abierto
#44,180 5 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@pavelfeldman ya está trabajando en esto.

Desde el 18/11/2026.

  • #44191 de @microsoft-playwright-automation — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
playwright, typescript
Área
backend, desktop

Línea de trabajo

Start by tracing how headed sessions track page closure and how the daemon decides whether to close the browser; the issue does not name the relevant files or tests. Reproduce by quitting the last headed Chrome window from the macOS Dock and checking whether the daemon still reports the session open. Done means that this action ends the session without treating tab-close or page-initiated window.close() as session termination. An open pull request already addresses the issue.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

agent-triage milestone

playwright-cli open --headed on macOS.
right-click → quit on the dock icon closes the window, but the main Google Chrome process (launched with --remote-debugging-pipe --no-startup-window) stays alive, and the daemon still reports the session open (tab-list shows about:blank). Since headed sessions have no idle timeout, the windowless process stays indefinitely. Because it's the same app bundle as the user's Chrome, it also stops the user's regular Chrome from opening tabs until it's killed in Activity Monitor.

Happy to open a PR with a fix where, in headed mode, if the last page is closed by something other than a CLI command (e.g. the user quitting Chrome from the dock or closing its last window), the daemon treats it as the user ending the session and closes the browser. Pages closed by tab-close or by window.close() from a page would not trigger it.

Lenguaje dominante
TypeScript
Estrellas
100k
Forks
6.9k
Merge medio
16 h 8 min
PR fusionados (30 d)
281

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/playwright

Todos los issues de microsoft/playwright

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.