Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(docs): docs links #19510

Merged
merged 2 commits into from
Dec 20, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/src/api/class-page.md
Original file line number Diff line number Diff line change
Expand Up @@ -825,7 +825,7 @@ Get the browser context that the page belongs to.
Only available for Chromium atm.
:::

Browser-specific Coverage implementation. See [Coverage](#class-coverage) for more details.
Browser-specific Coverage implementation. See [Coverage](./class-coverage) for more details.

## async method: Page.dblclick
* since: v1.8
Expand Down
2 changes: 1 addition & 1 deletion docs/src/api/class-playwright.md
Original file line number Diff line number Diff line change
Expand Up @@ -186,7 +186,7 @@ Playwright methods might throw errors if they are unable to fulfill a request. F
[`method: Locator.waitFor`] might fail if the selector doesn't match any nodes during the given timeframe.

For certain types of errors Playwright uses specific error classes. These classes are available via
[`playwright.errors`](#playwrighterrors).
[`playwright.errors`](#playwright-errors).

An example of handling a timeout error:

Expand Down
2 changes: 1 addition & 1 deletion docs/src/test-configuration-js.md
Original file line number Diff line number Diff line change
Expand Up @@ -435,7 +435,7 @@ const config: PlaywrightTestConfig = {
export default config;
```

However, most common ones like `headless` or `viewport` are available directly in the `use` section - see [basic options](#basic-options), [emulation](#emulation) or [network](#network).
However, most common ones like `headless` or `viewport` are available directly in the `use` section - see [basic options](#basic-options), [emulation](./emulation.md) or [network](#network).

## Explicit Context Creation and Option Inheritance

Expand Down
2 changes: 1 addition & 1 deletion docs/src/webview2.md
Original file line number Diff line number Diff line change
Expand Up @@ -428,6 +428,6 @@ public class Tests : WebView2Test

## Debugging

Inside your webview2 control, you can just right-click to open the context menu and select "Inspect" to open the DevTools or press <kbd>F12</kbd>. You can also use the [WebView2.OpenDevToolsWindow](https://docs.microsoft.com/en-us/dotnet/api/microsoft.web.webview2.wpf.webview2.opendevtoolswindow?view=webview2-dotnet-1.0.1343.22) method to open the DevTools programmatically.
Inside your webview2 control, you can just right-click to open the context menu and select "Inspect" to open the DevTools or press <kbd>F12</kbd>. You can also use the [WebView2.CoreWebView2.OpenDevToolsWindow](https://learn.microsoft.com/en-us/dotnet/api/microsoft.web.webview2.core.corewebview2.opendevtoolswindow?view=webview2-dotnet-1.0.1462.37) method to open the DevTools programmatically.

For debugging tests, see the Playwright [Debugging guide](./debug).