headed chrome can't be quit from macOS dock and also blocks user from creating new chrome windows
Maintainers usually reply within 1 day
@pavelfeldman is already working on this.
Since Nov 18, 2026.
- #44191 by @microsoft-playwright-automation — open
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- playwright, typescript
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- TypeScript
- Stars
- 100k
- Forks
- 6.9k
- Avg merge
- 16h 8m
- Merged PRs (30d)
- 281
Getting set up
- No 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 microsoft/playwright
-
[MCP]: page snapshots in .playwright-mcp/ are not git-ignored (.playwright-cli/ is, since #42318)Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoft/playwright#44289 ·
Maintainers usually reply within 1 day
-
agent-triage-done
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/playwright#44264 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
microsoft/playwright#44290 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
microsoft/playwright#44288 ·
Maintainers usually reply within 1 day
-
[Bug]: page.goto never returns for a load started as a newer service worker takes over (Chromium)Open
Difficulty 5/5 Over a week Newbie friendliness 12/100
microsoft/playwright#44287 ·
Maintainers usually reply within 1 day
All issues in microsoft/playwright
Similar issues
-
clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw#203385 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nwverse/persona#12800 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 Half a day Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
WISE-Community/WISE-Client#2404 ·
Maintainers usually reply within 1 day