From 04b16795ff202336e2dfc14291f62ca593b95add Mon Sep 17 00:00:00 2001 From: jfgreffier Date: Fri, 16 Dec 2022 12:43:30 +0100 Subject: [PATCH 1/2] fix(docs): docs links --- docs/src/api/class-page.md | 2 +- docs/src/api/class-playwright.md | 2 +- docs/src/test-configuration-js.md | 2 +- docs/src/webview2.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/src/api/class-page.md b/docs/src/api/class-page.md index 91fd49bba3d1c..5557aef326b4b 100644 --- a/docs/src/api/class-page.md +++ b/docs/src/api/class-page.md @@ -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 diff --git a/docs/src/api/class-playwright.md b/docs/src/api/class-playwright.md index 843b0b9f1ce3e..8d9a9235f2633 100644 --- a/docs/src/api/class-playwright.md +++ b/docs/src/api/class-playwright.md @@ -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: diff --git a/docs/src/test-configuration-js.md b/docs/src/test-configuration-js.md index 0e4c5893c0878..bed3b181680c0 100644 --- a/docs/src/test-configuration-js.md +++ b/docs/src/test-configuration-js.md @@ -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 diff --git a/docs/src/webview2.md b/docs/src/webview2.md index c9278345e88bd..731e6291f473d 100644 --- a/docs/src/webview2.md +++ b/docs/src/webview2.md @@ -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 F12. 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 F12. 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.1343.22) method to open the DevTools programmatically. For debugging tests, see the Playwright [Debugging guide](./debug). From 6b870d95fa4b430b2f0f3465cec84132b87a97a7 Mon Sep 17 00:00:00 2001 From: Max Schmitt Date: Tue, 20 Dec 2022 13:12:00 +0100 Subject: [PATCH 2/2] Update docs/src/webview2.md Signed-off-by: Max Schmitt --- docs/src/webview2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/webview2.md b/docs/src/webview2.md index 731e6291f473d..e1683a23788cb 100644 --- a/docs/src/webview2.md +++ b/docs/src/webview2.md @@ -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 F12. 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.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 F12. 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).