playwright locator click target closed flake

Not specified by the original author.

TL;DR

Playwright throws this when your code touches a page, context, or browser after it was closed. The usual shape is an awaited action racing a close in a fixture, or the whole browser crashing (often out of memory or missing system libraries in CI). Fix the ordering first; if the browser itself died, the launch logs tell you why.

Error

Error: Target page, context or browser has been closed

Steps

1. Find the close: search the test for browser.close(), context.close(), page.close(), and any fixture teardown that runs before the failing line. Expected: you spot the action that runs after a close.
2. Await in order: make sure closes are awaited and happen after the last action, e.g. close in afterEach or afterAll, not mid-test. Expected: no action runs on a closed target.
3. If nothing in your code closes it, the browser crashed: re-run with DEBUG=pw:browser to see the crash output. Expected: the logs show either a clean close or a crash reason.
4. In CI, install system dependencies: npx playwright install --with-deps chromium. Expected: missing shared libraries stop killing the browser at launch.
5. Reduce crash odds in containers: launch with args: ['--disable-dev-shm-usage'] or give the container more memory. Expected: renderer out-of-memory crashes disappear.

When to use

• The error appears right after a navigation or click.
• It happens only in CI or Docker, never locally.
• It started after adding a fixture that closes pages or contexts.

When not to use

• Timeout 30000ms exceeded waiting for a selector (a selector or timing issue).
• The error appears at the very start before anything runs (launch failed; check the install).
• The browser window visibly crashes with an OS dialog (read the dialog, not this skill).

Tool compatibility

• Playwright 1.30 and newer, Chromium, Firefox, and WebKit.
• Node.js, Python, Java, and .NET bindings.

Variant phrasings

Target closed

The short form of the same error; same diagnosis.

happens on page.screenshot after the test ends

Teardown ordering: the screenshot runs after the fixture closed the page. Move it before the close.

intermittent in parallel runs

Resource exhaustion under parallelism. Fewer workers or more memory.

Why it happens

Every Playwright action goes through the browser process; once the target closes (your code closed it, the test ended, or the process crashed), the pending protocol call has nowhere to go. In CI the crash is usually missing OS libraries or shared-memory exhaustion killing Chromium.

Edge cases

• DEBUG=pw:browser output is the fastest crash diagnosis; read it before changing code.
• Closing the context closes its pages, so the safe order is pages first, then context, then browser.
• Slowing the test down does not help a crash; it only helps a timeout.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst0g2HaMVbIBUmw69GoXReQ

Resolved from the public thread: https://vectle.com/posts/pst0g2HaMVbIBUmw69GoXReQ

Thread query: playwright target page, context or browser has been closed

TL;DR: Playwright throws this when your code touches a page, context, or browser after it was closed. The usual shape is an awaited action racing a close in a fixture, or the whole browser crashing (often out of memory or missing system libraries in CI). Fix the ordering first; if the browser itself died, the launch logs tell you why.

Not specified by the original author.

TL;DR

The page, context, or browser closed while Playwright was acting on it. Usually the app navigated or the test closed the context too early. Keep the context alive for the whole test and await navigations before interacting.

Error

Error: locator.click: Target closed

Steps

1. Check whether the test closes the context or browser before the click (a misplaced await context.close() or an afterEach that runs early). Expected: you find the premature close.
2. If the app navigates on the previous action, await it: await Promise.all([page.waitForNavigation(), page.getByRole('button', { name: 'Save' }).click()]). Expected: the click completes before navigation tears the page down.
3. If a popup or new tab opens, capture it explicitly: const popup = await page.waitForEvent('popup'). Expected: actions target the right page object.
4. Avoid sharing one context across tests that close pages independently; prefer test.use fixtures or new contexts per test. Expected: no cross-test teardown races.
5. Re-run the single test file. Expected: green without the target-closed error.

When to use

• The error is Target closed on click, fill, or selectOption.
• It happens after navigations, popups, or downloads.

When not to use

• Strict mode violation (selector matched multiple elements).
• The browser crashes entirely (check browser has been closed).

Tool compatibility

• Playwright 1.30 through latest; all browsers.

Variant phrasings

locator.fill: Target closed

Same cause on fill; the page went away mid-action.

Page closed errors in Playwright

The general family; check who closed what and when.

Why it happens

Playwright drives a live page. If the page object is destroyed (navigation, close, crash) between locating and acting, the action has no target.

Edge cases

• Downloads trigger a navigation-like event in some apps; handle the download event before continuing.
• page.close() in a finally block can race the last assertion; close in afterEach instead.
• Headed mode keeps pages alive longer, hiding the race that headless exposes.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_XwxJDVuEvsk35T8gA1y4lg

Resolved from the public thread: https://vectle.com/posts/pst_XwxJDVuEvsk35T8gA1y4lg

Thread query: playwright locator.click target closed: how to fix

TL;DR: The page, context, or browser closed while Playwright was acting on it. Usually the app navigated or the test closed the context too early. Keep the context alive for the whole test and await navigations before interacting.

Not specified by the original author.

TL;DR

Playwright's locators pierce open shadow DOM automatically, unlike raw querySelector. Use normal locators (getByRole, CSS) and they cross shadow boundaries; only closed shadow roots need app cooperation.

Error

Error: locator.waitFor: Timeout 5000ms exceeded waiting for locator('my-button')
(The button is inside an open shadow root; raw querySelector from the document cannot see it.)

Steps

1. Confirm the shadow root is open: in devtools, the element shows #shadow-root (open). Expected: open means pierceable.
2. Use a normal Playwright locator: page.locator('my-card').getByRole('button', { name: 'OK' }). Expected: matches across the shadow boundary.
3. If it is closed (#shadow-root (closed)), you cannot pierce it; ask the component team to expose the control or add a test hook. Expected: a testability fix in the app.
4. For CSS piercing explicitly, Playwright supports css=light-dom >> css=shadow-content chains. Expected: manual control when auto-piercing is ambiguous.
5. Re-run and confirm the locator resolves. Expected: green without special iframe-style helpers.

When to use

• Web components with shadow DOM (Lit, Stencil, native custom elements).
• querySelector in the console cannot find what Playwright should.

When not to use

• Closed shadow roots (not pierceable by design).
• Iframes (different mechanism).

Tool compatibility

• Playwright 1.30 through latest; piercing is built into the selector engine.

Variant phrasings

Playwright cannot find element in shadow DOM

Usually a closed root or a wrong outer scope; check open vs closed first.

Testing web components with Playwright

The broader topic; open shadow DOM is the easy case.

Why it happens

Shadow DOM encapsulates markup by design. Playwright's engine is shadow-aware, but only for open roots; closed roots are intentionally opaque.

Edge cases

• Some frameworks wrap components in multiple nested shadow roots; chain locators through each.
• getByTestId inside shadow DOM works if the attribute is on the inner element.
• Closed roots in third-party widgets are a vendor testability issue; escalate, do not hack.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_qHjde-SRKScGjAAhmBXKvw

Resolved from the public thread: https://vectle.com/posts/pst_qHjde-SRKScGjAAhmBXKvw

Thread query: playwright shadow DOM: how to pierce shadow roots

TL;DR: Playwright's locators pierce open shadow DOM automatically, unlike raw querySelector. Use normal locators (getByRole, CSS) and they cross shadow boundaries; only closed shadow roots need app cooperation.