docs(dotnet): generate 1.11 api off tot (#6564)

This commit is contained in:
Pavel Feldman 2021-05-13 12:24:20 -07:00 committed by GitHub
parent c4321887d1
commit 81a57ea2ac
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 7 additions and 0 deletions

View File

@ -144,6 +144,7 @@ cases).
::: :::
## event: BrowserContext.request ## event: BrowserContext.request
* langs: js, python, java
- argument: <[Request]> - argument: <[Request]>
Emitted when a request is issued from any pages created through this context. Emitted when a request is issued from any pages created through this context.
@ -154,6 +155,7 @@ In order to intercept and mutate requests, see [`method: BrowserContext.route`]
or [`method: Page.route`]. or [`method: Page.route`].
## event: BrowserContext.requestFailed ## event: BrowserContext.requestFailed
* langs: js, python, java
- argument: <[Request]> - argument: <[Request]>
Emitted when a request fails, for example by timing out. To only listen for Emitted when a request fails, for example by timing out. To only listen for
@ -165,6 +167,7 @@ with [`event: BrowserContext.requestFinished`] event and not with [`event: Brows
::: :::
## event: BrowserContext.requestFinished ## event: BrowserContext.requestFinished
* langs: js, python, java
- argument: <[Request]> - argument: <[Request]>
Emitted when a request finishes successfully after downloading the response body. For a successful response, the Emitted when a request finishes successfully after downloading the response body. For a successful response, the
@ -172,6 +175,7 @@ sequence of events is `request`, `response` and `requestfinished`. To listen for
successful requests from a particular page, use [`event: Page.requestFinished`]. successful requests from a particular page, use [`event: Page.requestFinished`].
## event: BrowserContext.response ## event: BrowserContext.response
* langs: js, python, java
- argument: <[Response]> - argument: <[Response]>
Emitted when [response] status and headers are received for a request. For a successful response, the sequence of events Emitted when [response] status and headers are received for a request. For a successful response, the sequence of events
@ -1164,6 +1168,7 @@ current working directory. If no path is provided, storage
state is still returned, but won't be saved to the disk. state is still returned, but won't be saved to the disk.
## property: BrowserContext.tracing ## property: BrowserContext.tracing
* langs: js, python, java
- type: <[Tracing]> - type: <[Tracing]>
## async method: BrowserContext.unroute ## async method: BrowserContext.unroute

View File

@ -1,4 +1,5 @@
# class: Tracing # class: Tracing
* langs: js, python, java
API for collecting and saving Playwright traces. Playwright traces can be opened using the Playwright CLI after API for collecting and saving Playwright traces. Playwright traces can be opened using the Playwright CLI after
Playwright script runs. Playwright script runs.

View File

@ -680,6 +680,7 @@ Maximum time in milliseconds to wait for the browser instance to start. Defaults
disable timeout. disable timeout.
## browser-option-tracedir ## browser-option-tracedir
* langs: js, python, java
- `traceDir` <[path]> - `traceDir` <[path]>
If specified, traces are saved into this directory. If specified, traces are saved into this directory.