From 8733b96b96a89a80b59c6d3f93f7f9ba651a8e02 Mon Sep 17 00:00:00 2001 From: Alex Rudenko Date: Thu, 7 Dec 2023 08:25:25 +0100 Subject: [PATCH] docs: fix and reorder (#11509) --- docs/webdriver-bidi.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/webdriver-bidi.md b/docs/webdriver-bidi.md index 47c50f1ab89..e20408571f8 100644 --- a/docs/webdriver-bidi.md +++ b/docs/webdriver-bidi.md @@ -9,7 +9,7 @@ resources if you want to learn more about WebDriver BiDi: ## Automate with Chrome and Firefox -Firefox support has almost reaching feature parity with the previous CDP-based +Firefox support has almost reached feature parity with the previous CDP-based implementation. To see which features are fully supported with WebDriver BiDi we used the [Puppeteer test suite](https://puppeteer.github.io/ispuppeteerwebdriverbidiready/). Currently, we still have fewer than @@ -19,11 +19,6 @@ CDP implementation in Firefox but we also have more than [82](https://puppeteer.github.io/ispuppeteerwebdriverbidiready/firefox-delta.json) new tests that work with WebDriver BiDi and that didn't work with CDP. -For Chrome, around 68% of the tests are currently passing with WebDriver BiDi so -the CDP-based implementation remains more powerful. Some of the Puppeteer -functionality is relying on CDP even with WebDriver BiDi enabled. Therefore, the -test pass rate is currently higher than that one of Firefox. - Example of launching Firefox with WebDriver BiDi: ```ts @@ -38,6 +33,11 @@ const page = await browser.newPage(); await browser.close(); ``` +For Chrome, around 68% of the tests are currently passing with WebDriver BiDi so +the CDP-based implementation remains more powerful. Some of the Puppeteer +functionality is relying on CDP even with WebDriver BiDi enabled. Therefore, the +test pass rate is currently higher than that one of Firefox. + Example of launching Chrome with WebDriver BiDi: ```ts