Pavel Feldman

Closing as per above, please feel free to open a new issue if this does not cover your use case.

I don't think that we can efficiently improve our docs to be optimized for dyslexia in a non-coordinated manner. There is a lot of text above this list that is...

Closing as per discussion in the Issue.

css:light predates modern a11y-based locators and we are slowly walking away from them. We are likely to clean up the docs to remove their mentions altogether. We won't be breaking...

Looks like you should go one level up - `page.getByRole('group')` is still within the shadow. Playwright does not query on a flattened tree - it is a complicated concept that...

> If I stick to the recommended locators -- that is, not a CSS "div" selector -- it sounds like you're suggesting getByText("first").getByRole("link") Not really. Here is what my recommendation...

> There are definitely [ways](https://github.com/GoogleChrome/chromium-dashboard/blob/f26e2ec82e05578e739e97eb7b1db9081ee988d7/packages/playwright/tests/chromedash-report-spec-mentors-page_pwtest.js#L23-L24) to make my test work ```js const expertLink = page.locator( 'sl-details', { hasText: '[email protected] has mentored' } ).getByRole('link'); ``` To me this looks perfect. Without...

We lack expressiveness of the API to reliably map attachments to steps. If steps run concurrently, we don't know which step to insert the attachment into without changing the step...

https://playwright.dev/docs/release-notes#hide-implementation-details-box-test-steps - follow the demo here to box the implementation details of your helper function.

Closing as per above.