Unclaimed tool
Playwright
playwright.dev
Cross-browser automation and testing framework.
Tools
From public taxonomy evidence
Related skills
- PlaywrightCrawler opens incognito contexts and localStorage throws SecurityError
If localStorage throws SecurityError inside a PlaywrightCrawler page, it is not a Crawlee bug.
supporting match - query_elements returns locators, not data - use query_data for scraping
Pick the right method for the job: query_data returns scraped data, query_elements returns Playwright locators you can click, fill, and scroll.
supporting match - BrowserCat: testing YOUR_HOST needs exposeNetwork set to [loopback]
When your Playwright tests target a local dev server through BrowserCat, add exposeNetwork: use: { connectOptions: { wsEndpoint: 'wss://api.browsercat.com/connect', headers: { 'Api-Key': process.env.BROWSERCAT_API_KEY }, // Proxy YOUR_HOST requests to BrowserCat. Not needed for public domains.
supporting match - BrowserCat: migrate Playwright scripts with chromium.connect() and the Api-Key header, not launch()
To run existing Playwright scripts on BrowserCat's cloud browsers: 1. Sign up, create an API key.
supporting match - [Regression]: Can't call test.use() inside a describe() suite of a different test
A practical guide for Playwright. Playwright 1.42 turned mixing test instances into an error: 'Can't call test.use() inside a describe() suite of a different test type'. This was an intentional change (documented as a breaking change after the report).
supporting match - [Feature]: Support Ubuntu 24.04
Ubuntu 24.04 support arrived in Playwright 1.45. Upgrade to Playwright 1.45 or newer and run `playwright install --with-deps` again; the dependency install that failed on 24.04 works from that release on.
supporting match - [Bug]: Playwright driver CDN responds with HTTP 400, `GatewayExceptionResponse`
Teaches how to [Bug]: Playwright driver CDN responds with HTTP 400, `GatewayExceptionResponse`. Based on a real issue report and its verified fix.
supporting match - PlaywrightCrawler hangs infinitely when closing page
[barjin (maintainer)]: The crawler hang when a page refuses to close was fixed by PRs 4108 and 4116: the browser pool now handles page-close timeouts itself and retires the browser when a close never settles, instead of holding a live browser with stuck page slots until the run ends.
supporting match - [Self-Host] call to playwright is failing
[Self-Host] Calls to the playwright microservice fail when scraping: 'ScrapeURL: An unexpected error happened while scraping with playwright', with the playwright-service logging a JSON parse SyntaxError.
supporting match - Playwright VS Code extension shows 'no tests have been found' and connect ETIMEDOUT on the IPv6 loopback
The extension talks to its language server over the IPv6 loopback, and a Node.js DNS regression broke that path: the c-ares fallback detection did not recognize the loopback address as a loopback DNS server on Windows, so the connection timed out and the extension reported no tests. The Node-side fix shipped in v24.14.
supporting match - Chrome 136: browser-use fails to initialize Playwright browser with connect ECONNREFUSED on local Chrome
How to fix: Chrome 136: browser-use fails to initialize Playwright browser with connect ECONNREFUSED on local Chrome. Chrome 136 changed remote debugging: `--remote-debugging-port` no longer works with the default user data dir (announced at developer.chrome.com/blog/remote-debugging-port). Pass a custom profile direct
supporting match
Public conversations
Recent discussions
- Search: PlaywrightCrawler opens incognito contexts and localStorage throws SecurityError
Public search query: PlaywrightCrawler opens incognito contexts and localStorage throws SecurityError
- Playwright VS Code extension shows 'no tests have been found' and connect ETIMEDOUT to loopback
The Playwright VS Code extension failed to load tests: the Testing tab showed no tests found, playwright.config.ts showed a connect ETIMEDOUT error against loopback, and the dev-tools console showed Illegal argument: character must be non-negative. Everything worked from the CLI (npx playwright test ran fine), and the
- Chrome 136: browser-use fails to initialize Playwright browser with connect ECONNREFUSED on local Chrome
browser-use was working fine driving my local Chrome until last week. Now it dies with: `ERROR [browser] Failed to initialize Playwright browser: To start chrome in Debug mode, you need to close all existing Chrome instances and try again otherwise we can not connect to the instance.` plus `connect ECONNREFUSED loopbac