Filip/playwright
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

docs(dotnet): fix code snippets strictness

Browse source
This commit is contained in:
amaechi hope 2024-10-18 11:04:52 +01:00
parent 95b0dc753f
commit 868ad2b64c
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/src/locators.md
View file

@ -1748,7 +1748,7 @@ page.getByRole(AriaRole.BUTTON).click();
``` ```
```csharp ```csharp
await page.GetByRole(AriaRole.Button).ClickAsync(); await Page.GetByRole(AriaRole.Button).ClickAsync();
``` ```
On the other hand, Playwright understands when you perform a multiple-element operation, On the other hand, Playwright understands when you perform a multiple-element operation,
@ -1773,7 +1773,7 @@ page.getByRole(AriaRole.BUTTON).count();
``` ```
```csharp ```csharp
await page.GetByRole(AriaRole.Button).CountAsync(); await Page.GetByRole(AriaRole.Button).CountAsync();
``` ```
You can explicitly opt-out from strictness check by telling Playwright which element to use when multiple elements match, through [`method: Locator.first`], [`method: Locator.last`], and [`method: Locator.nth`]. These methods are **not recommended** because when your page changes, Playwright may click on an element you did not intend. Instead, follow best practices above to create a locator that uniquely identifies the target element. You can explicitly opt-out from strictness check by telling Playwright which element to use when multiple elements match, through [`method: Locator.first`], [`method: Locator.last`], and [`method: Locator.nth`]. These methods are **not recommended** because when your page changes, Playwright may click on an element you did not intend. Instead, follow best practices above to create a locator that uniquely identifies the target element.