From 69c5b2a3b6347acfb04a78312129bf28a0c0cc45 Mon Sep 17 00:00:00 2001 From: Pavel Feldman Date: Thu, 23 Jan 2020 17:54:01 -0800 Subject: [PATCH] docs: clarify Puppeteer active status (#619) --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index da6f7b8d2bea0..ea94b05337cdd 100644 --- a/README.md +++ b/README.md @@ -129,6 +129,8 @@ Check out our [contributing guide](https://github.com/microsoft/playwright/blob/ **Q: How does Playwright relate to [Puppeteer](https://github.com/puppeteer/puppeteer)?** +Puppeteer is a Node library which provides a high-level API to control Chrome or Chromium over the DevTools Protocol. Puppeteer project is active and is maintained by Google. + We are the same team that built Puppeteer. Puppeteer proved that there is a lot of interest in the new generation of ever-green, capable and reliable automation drivers. With Playwright, we'd like to take it one step further and offer the same functionality for **all** the popular rendering engines. We'd like to see Playwright vendor-neutral and shared governed. With Playwright, we are making the APIs more testing-friendly as well. We are taking the lessons learned from Puppeteer and incorporate them into the API, for example, user agent / device emulation is set up consistently on the `BrowserContext` level to enable multi-page scenarios, `click` waits for the element to be available and visible by default, there is a way to wait for network and other events, etc.