Update puppeteer to 19.7.3
Bug: none
Change-Id: I7e8ef149b66c6376ee728df1ee4b7c8c14803a78
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4311823
Reviewed-by: Nikolay Vitkov <[email protected]>
Reviewed-by: Simon Zünd <[email protected]>
Commit-Queue: Randolf Jung <[email protected]>
diff --git a/node_modules/chromium-bidi/README.md b/node_modules/chromium-bidi/README.md
new file mode 100644
index 0000000..74e55f4
--- /dev/null
+++ b/node_modules/chromium-bidi/README.md
@@ -0,0 +1,395 @@
+# WebDriver BiDi for Chromium [](https://www.npmjs.com/package/chromium-bidi)
+
+
+
+
+
+
+
+
+This is an implementation of the
+[WebDriver BiDi](https://w3c.github.io/webdriver-bidi/) protocol with some
+extensions (**BiDi+**)
+for Chromium, implemented as a JavaScript layer translating between BiDi and CDP,
+running inside a Chrome tab.
+
+Current status can be checked
+at [WPT WebDriver BiDi status](https://wpt.fyi/results/webdriver/tests/bidi).
+
+## BiDi+
+
+**"BiDi+"** is an extension of the WebDriver BiDi protocol. In addition to [WebDriver BiDi](https://w3c.github.io/webdriver-bidi/) it has:
+
+### Command `cdp.sendCommand`
+
+```cddl
+CdpSendCommandCommand = {
+ method: "cdp.sendCommand",
+ params: ScriptEvaluateParameters,
+}
+
+CdpSendCommandParameters = {
+ cdpMethod: text,
+ cdpParams: any,
+ cdpSession?: text,
+}
+
+CdpSendCommandResult = {
+ result: any,
+ cdpSession: text,
+}
+```
+
+The command runs the
+described [CDP command](https://chromedevtools.github.io/devtools-protocol)
+and returns result.
+
+### Command `cdp.getSession`
+
+```cddl
+CdpGetSessionCommand = {
+ method: "cdp.sendCommand",
+ params: ScriptEvaluateParameters,
+}
+
+CdpGetSessionParameters = {
+ context: BrowsingContext,
+}
+
+CdpGetSessionResult = {
+ cdpSession: text,
+}
+```
+
+The command returns the default CDP session for the selected browsing context.
+
+### Event `cdp.eventReceived`
+
+```cddl
+CdpEventReceivedEvent = {
+ method: "cdp.eventReceived",
+ params: ScriptEvaluateParameters,
+}
+
+CdpEventReceivedParameters = {
+ cdpMethod: text,
+ cdpParams: any,
+ cdpSession: string,
+}
+```
+
+The event contains a CDP event.
+
+### Field `channel`
+
+Each command can be extended with a `channel`:
+
+```cddl
+Command = {
+ id: js-uint,
+ channel?: text,
+ CommandData,
+ Extensible,
+}
+```
+
+If provided and non-empty string, the very same `channel` is added to the response:
+
+```cddl
+CommandResponse = {
+ id: js-uint,
+ channel?: text,
+ result: ResultData,
+ Extensible,
+}
+
+ErrorResponse = {
+ id: js-uint / null,
+ channel?: text,
+ error: ErrorCode,
+ message: text,
+ ?stacktrace: text,
+ Extensible
+}
+```
+
+When client uses
+commands [`session.subscribe`](https://w3c.github.io/webdriver-bidi/#command-session-subscribe)
+and [`session.unsubscribe`](https://w3c.github.io/webdriver-bidi/#command-session-unsubscribe)
+with `channel`, the subscriptions are handled per channel, and the corresponding
+`channel` filed is added to the event message:
+
+```cddl
+Event = {
+ channel?: text,
+ EventData,
+ Extensible,
+}
+```
+
+## Dev Setup
+
+### `npm`
+
+This is a Node.js project, so install dependencies as usual:
+
+```sh
+npm install
+```
+
+### pre-commit.com integration
+
+Refer to the documentation at [.pre-commit-config.yaml](.pre-commit-config.yaml).
+
+### Starting the Server
+
+This will run the server on port `8080`:
+
+```sh
+npm run server
+```
+
+Use the `PORT=` environment variable or `--port=` argument to run it on another port:
+
+```sh
+PORT=8081 npm run server
+npm run server -- --port=8081
+```
+
+Use the `DEBUG` environment variable to see debug info:
+
+```sh
+DEBUG=* npm run server
+```
+
+Use the CLI argument `--headless=false` to run browser in headful mode:
+
+```sh
+npm run server -- --headless=false
+```
+
+Use the `CHANNEL=...` environment variable or `--channel=...` argument with one of
+the following values to run the specific Chrome channel: `chrome`,
+`chrome-beta`, `chrome-canary`, `chrome-dev`.
+
+The requested Chrome version should be installed.
+
+```sh
+CHANNEL=chrome-dev npm run server
+npm run server -- --channel=chrome-dev
+```
+
+### Starting on Linux and Mac
+
+TODO: verify if it works on Windows.
+
+You can also run the server by using script `./runBiDiServer.sh`. It will write
+output to the file `log.txt`:
+
+```sh
+./runBiDiServer.sh --port=8081 --headless=false
+```
+
+## Running
+
+### Unit tests
+
+Running:
+
+```sh
+npm test
+```
+
+### E2E tests
+
+The E2E tests are written using Python, in order to learn how to eventually do
+this in web-platform-tests.
+
+### Installation
+
+Python 3.6+ and some dependencies are required:
+
+```sh
+python3 -m pip install --user -r tests/requirements.txt
+```
+
+### Running
+
+The E2E tests require BiDi server running on the same host. By default, tests
+try to connect to the port `8080`. The server can be run from the project root:
+
+```sh
+npm run e2e
+```
+
+Use the `PORT` environment variable to connect to another port:
+
+```sh
+PORT=8081 npm run e2e
+```
+
+### Examples
+
+Refer to [examples/README.md](examples/README.md).
+
+## WPT (Web Platform Tests)
+
+WPT is added as
+a [git submodule](https://git-scm.com/book/en/v2/Git-Tools-Submodules). To get run
+WPT tests:
+
+### Check out and setup WPT
+
+#### 1. Check out WPT
+
+```sh
+git submodule update --init
+```
+
+#### 2. Go to the WPT folder
+
+```sh
+cd wpt
+```
+
+#### 3. Set up virtualenv
+
+Follow the [_System
+Setup_](https://web-platform-tests.org/running-tests/from-local-system.html#system-setup)
+instructions.
+
+#### 4. Setup `hosts` file
+
+Follow
+the [`hosts` File Setup](https://web-platform-tests.org/running-tests/from-local-system.html#hosts-file-setup)
+instructions.
+
+##### 4.a On Linux, macOS or other UNIX-like system
+
+```sh
+./wpt make-hosts-file | sudo tee -a /etc/hosts
+```
+
+##### 4.b On **Windows**
+
+This must be run in a PowerShell session with Administrator privileges:
+
+```sh
+python wpt make-hosts-file | Out-File $env:SystemRoot\System32\drivers\etc\hosts -Encoding ascii -Append
+```
+
+If you are behind a proxy, you also need to make sure the domains above are excluded
+from your proxy lookups.
+
+#### 5. Set `WPT_BROWSER_PATH`
+
+Set the `WPT_BROWSER_PATH` environment variable to a Chrome, Edge or Chromium binary to launch.
+For example, on macOS:
+
+```sh
+# Chrome
+export WPT_BROWSER_PATH="/Applications/Google Chrome Canary.app/Contents/MacOS/Google Chrome Canary"
+export WPT_BROWSER_PATH="/Applications/Google Chrome Dev.app/Contents/MacOS/Google Chrome Dev"
+export WPT_BROWSER_PATH="/Applications/Google Chrome Beta.app/Contents/MacOS/Google Chrome Beta"
+export WPT_BROWSER_PATH="/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"
+export WPT_BROWSER_PATH="/Applications/Chromium.app/Contents/MacOS/Chromium"
+
+# Edge
+export WPT_BROWSER_PATH="/Applications/Microsoft Edge Canary.app/Contents/MacOS/Microsoft Edge Canary"
+export WPT_BROWSER_PATH="/Applications/Microsoft Edge.app/Contents/MacOS/Microsoft Edge"
+```
+
+### Run WPT tests
+
+#### 1. Make sure you have Chrome Dev installed
+
+https://www.google.com/chrome/dev/
+
+#### 2. Build ChromeDriver BiDi
+
+Oneshot:
+
+```sh
+npm run build
+```
+
+Continuously:
+
+```sh
+npm run watch
+```
+
+#### 3. Run
+
+```sh
+./wpt/wpt run \
+ --webdriver-binary ./runBiDiServer.sh \
+ --binary "$WPT_BROWSER_PATH" \
+ --manifest ./wpt/MANIFEST.json \
+ --metadata ./wpt-metadata \
+ chromium \
+ webdriver/tests/bidi/
+```
+
+### Update WPT expectations if needed
+
+#### 1. Run WPT tests with custom `log-wptreport`:
+
+```sh
+./wpt/wpt run \
+ --webdriver-binary ./runBiDiServer.sh \
+ --binary "$WPT_BROWSER_PATH" \
+ --manifest ./wpt/MANIFEST.json \
+ --metadata ./wpt-metadata \
+ --log-wptreport wptreport.json \
+ chromium \
+ webdriver/tests/bidi/
+```
+
+#### 2. Update expectations based on the previous test run:
+
+```sh
+./wpt/wpt update-expectations \
+ --product chromium \
+ --manifest ./wpt/MANIFEST.json \
+ --metadata ./wpt-metadata \
+ ./wptreport.json
+```
+
+## How does it work?
+
+The architecture is described in the
+[WebDriver BiDi in Chrome Context implementation plan](https://docs.google.com/document/d/1VfQ9tv0wPSnb5TI-MOobjoQ5CXLnJJx9F_PxOMQc8kY)
+.
+
+There are 2 main modules:
+
+1. backend WS server in `src`. It runs webSocket server, and for each ws connection
+ runs an instance of browser with BiDi Mapper.
+2. front-end BiDi Mapper in `src/bidiMapper`. Gets BiDi commands from the backend,
+ and map them to CDP commands.
+
+### Contributing
+
+The BiDi commands are processed in the `src/bidiMapper/commandProcessor.ts`. To add a
+new command, add it to `_processCommand`, write and call processor for it.
+
+### Publish new `npm` release
+
+1. On the `main` branch, bump the chromium-bidi version number in `package.json`:
+
+ ```sh
+ npm version patch -m 'Release v%s'
+ ```
+
+ Instead of `patch`, use `minor` or `major` [as needed](https://semver.org/).
+
+ Note that this produces a Git commit + tag.
+
+1. Push the release commit and tag:
+
+ ```sh
+ git push && git push --tags
+ ```
+
+ Our CI then automatically publishes the new release to npm.
