Skip to content

docs: Playwright/Puppeteer/Selenium compatibility#12

Open
iWedmak wants to merge 3 commits into
masterfrom
docs/playwright-puppeteer-selenium-compat
Open

docs: Playwright/Puppeteer/Selenium compatibility#12
iWedmak wants to merge 3 commits into
masterfrom
docs/playwright-puppeteer-selenium-compat

Conversation

@iWedmak

@iWedmak iWedmak commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Добавлен раздел о совместимости с Playwright, Puppeteer и Selenium — Ceki использует raw CDP, те же методы и параметры.

ceki-plugin and others added 3 commits July 17, 2026 06:52
…le, MCP, anti-detect tools

- Add feature comparison table (residential IPs, human mimicry, captcha solving, MCP)
- Add Playwright → Ceki side-by-side migration example (Python)
- Add undetected-chromedriver and selenium-wire migration notes
- Add MCP section showing zero-code browser tools for AI agents
- Add compatibility badge at top of README
@iWedmak

iWedmak commented Jul 17, 2026

Copy link
Copy Markdown
Contributor Author

Fix #3: Add Known Differences section + Fix #4: Russian → English

1. Translate Russian lines in Per-framework migration

- - **undetected-chromedriver** — больше не нужен. Ceki предоставляет реальный fingerprint браузера реального человека + резидентный IP. Никаких патчей WebDriver.
- - **selenium-wire** — перехват запросов: `browser.send({"method": "Network.enable"})` + подписка на событие `Network.responseReceived`.
+ - **undetected-chromedriver** — no longer needed. Ceki provides a real human browser fingerprint + residential IP. No WebDriver patches required.
+ - **selenium-wire** — request interception: `browser.send({"method": "Network.enable"})` + subscribe to `Network.responseReceived` events.

2. Add Known Differences section

Insert after the browser.send() explanation paragraph, before ## Environment Variables:

### Known Differences

Ceki's CDP-over-WSS relay is not a direct local CDP pipe — a few differences to keep in mind when migrating from Playwright / Puppeteer / Selenium:

- **No CSS selectors on interaction methods**`click`, `type`, and `scroll` take viewport coordinates, not CSS selectors. For element-based selection, use `Runtime.evaluate` to get bounding rects, then pass coordinates.
- **Speed** — each command travels over the WebSocket relay with ~50–200ms round-trip (internet-latency dependent, unlike local CDP which is sub-millisecond). Batch operations in a single `Runtime.evaluate` where possible, rather than chaining many small CDP calls.
- **120s grace window** — after each command there's a 120s window before the session auto-closes. This is by design for workflow chaining, but long-running idle sessions will need a keepalive.
- **Runtime.evaluate serialization** — CDP's `Runtime.evaluate` returns JSON-serializable values only. Functions, symbols, DOM nodes, and circular references are not transferable. Use `--returnByValue` explicitly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant